Page MenuHomeFreeBSD

Cleanup patching of static content with sed.
ClosedPublic

Authored by mat on Mon, Jun 17, 8:58 PM.

Diff Detail

Repository
rD FreeBSD doc repository
Lint
Automatic diff as part of commit; lint not applicable.
Unit
Automatic diff as part of commit; unit tests not applicable.

Event Timeline

mat created this revision.Mon, Jun 17, 8:58 PM
adamw added a subscriber: adamw.Mon, Jun 17, 9:01 PM
adamw added inline comments.
en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml
7600 ↗(On Diff #58749)

This version has ${PREFIX}, but the one above has ${LOCALBASE}.

en_US.ISO8859-1/books/porters-handbook/slow-porting/chapter.xml
422 ↗(On Diff #58749)

This should be a semicolon, not a comma.

mat marked an inline comment as done.Thu, Jun 20, 10:56 AM
mat added inline comments.
en_US.ISO8859-1/books/porters-handbook/slow-porting/chapter.xml
422 ↗(On Diff #58749)

This seems off:

Do not use it to replace static content; use patch files for that.

For me, semicolon is used to separate two non related clauses, which could be separate sentences. Here, the two clauses are related and the second emphasizes the first.

mat updated this revision to Diff 58829.Thu, Jun 20, 10:57 AM
  • Be consistent.
adamw added inline comments.Thu, Jun 20, 12:22 PM
en_US.ISO8859-1/books/porters-handbook/slow-porting/chapter.xml
422 ↗(On Diff #58749)

The problem is that with a comma, one of the clauses must be dependent (i.e. a non-complete sentence). Here, both clauses are complete sentences, making it what's called a "comma splice."

I fully agree that the semicolon is weird there. Perhaps "You must use patch files instead of sed to replace static content." Or something like that.

mat marked 2 inline comments as done.Thu, Jun 20, 2:36 PM
This revision was not accepted when it landed; it landed in state Needs Review.
This revision was automatically updated to reflect the committed changes.