08.11.2015 01:34, Arbiel (gmx) пишет:
What is the procedure to write a documentation patch ?
E-h-h ... not sure I grok it ... you just send patch to
[email protected]. Patch should be based on current GIT master
(https://savannah.gnu.org/git/?group=grub). If possible, just use "git
send-email"; second best is to attach result of "git format-patch" (or,
if you are sure your client does not mangle long lines, inline it).
Unless you have long running development branch it is better to compact
everything in single commit. Simplified workflow would be something like
git clone ...
git checkout -b fix-grubenv-doc master
vi docs/grub.texi
git commit (start subject with start subject with "[PATCH] doc: ..."
check it builds, look with "info ./docs/grub.info" whether results are OK
git send-email master..HEAD
... you have something to fix as results of review ...
vi docs/grub.texi
git commit --amend ... (mark it as [PATCH v2])
git send-email
... rinse and repeat
But in general it is better to have patch in *any* format than none at
all, so use whatever tools and workflow you are comfortable with.
_______________________________________________
Help-grub mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/help-grub
