Note that after "git mv working-copy local-clone" and editing
local-clone/chapter.xml, git seems to think they're unrelated files.
Sorry about that.
Have you checked with xmllint?
My initial impression is that this looks good apart from a few nits, but if at all possible I'd like to hear from others too.
To that end, I've reached out OOB and hope to hear back.
I'll also note that I've checked, and it builds fine.
What prompted the use of pulls and merges being fast-forward only?
It's my understanding that to avoid merge commits (ie. the commits that say "Merge branch ..", rebase is to be used liberally both on branches before and after merging.
is a.dev-commits-doc-all.url defined anywhere?
I can't seem to find it, and xmllint complains about it.
Haven't run it through xmllint or igor yet, I first wanted to get a substantive review on my first draft. I will do so before submitting a 2nd draft, although perhaps I should wait to hear from Carlavilla before doing that. What's their username here?
https://github.com/bsdimp/freebsd-git-docs/blob/main/doc-cvt.md (which I used liberally throughout drafting this) and specifically the uses of that option under "Keeping current".
Did I misunderstand something?
Courtesy of grep -r:
./en_US.ISO8859-1/share/xml/mailing-lists.ent:<!ENTITY a.dev-commits-doc-all.url "&a.mailman.listinfo;/dev-commits-doc-all">
@carlavilla is their username - I've also gone ahead and added them as a reviewer, just in case.
Ah, no - that makes sense.
Welp, now I just feel foolish. :)
The problem here is not to convert this to AsciiDoctor, is how to fit all of these new content into the new FDP...
I'm going to propose something to you @pauamma_gundo.com
What do you think if we wait until the migration is complete and after that I'll convert all of this to AsciiDoctor and
we'll look how to add all of these information to the new FDP?
In this way you're not gonna lose of this work.
Apart of that, thanks for all your work in the documentation :)