Page MenuHomeFreeBSD

Reindent last update after adding <sect3>
ClosedPublic

Authored by mat on Apr 3 2015, 11:50 AM.
Tags
None
Referenced Files
Unknown Object (File)
Wed, Apr 24, 11:05 PM
Unknown Object (File)
Mar 15 2024, 7:15 AM
Unknown Object (File)
Mar 15 2024, 6:38 AM
Unknown Object (File)
Dec 20 2023, 5:22 AM
Unknown Object (File)
Nov 20 2023, 2:08 PM
Unknown Object (File)
Nov 12 2023, 1:09 AM
Unknown Object (File)
Nov 11 2023, 1:10 PM
Unknown Object (File)
Nov 7 2023, 10:10 AM
Subscribers

Details

Reviewers
gjb
wblock

Diff Detail

Repository
rD FreeBSD doc repository - subversion
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

mat retitled this revision from to Reindent last update after adding <sect3>.
mat updated this object.
mat edited the test plan for this revision. (Show Details)
mat added reviewers: wblock, gjb.
mat added a subscriber: Doc Committers.

Wondering if I should not reindent/rewrap all the book, while I'm at it...

In D2217#4, @mat wrote:

Wondering if I should not reindent/rewrap all the book, while I'm at it...

Because of our translation process, I've gone to saving massive whitespace updates for after content changes. In this case, it would be good to fix the whitespace in this whole chapter. But doing the whole book at one time is not necessary.

mat edited edge metadata.

Do the whole chapter.

I tried to minimize changes, while keeping igor happy.

en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml
173

Usually, I re-wrap the whole paragraph so there are no short lines. But it is not necessary.

4484

This is not a whitespace change, and should not be mixed with the rest of this patch. Errors like this are often found during whitespace fixes, so a small content patch after the whitespace one is common.

en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml
173

I started doing that, but the paragraph was not loosing a line, and it was adding a lot of churn that would make svn blame even harder.

4484

While not a whitespace change, it is definitively something translators can ignore. I have a s/be be/be/ lying somewhere else. I can undo those and commit them afterwards, sure.

en_US.ISO8859-1/books/porters-handbook/makefiles/chapter.xml
4484

Yes, please do that. We want to keep content changes separate. At least until we can get a better setup for translators.

Undo non whitespace changes.

wblock edited edge metadata.

Good. Please build-test before commit. Thanks!

This revision is now accepted and ready to land.Apr 8 2015, 2:13 AM