[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Locating a configuration file (*.cfg)

From: Andrei Borzenkov
Subject: Re: Locating a configuration file (*.cfg)
Date: Sun, 8 Nov 2015 09:46:44 +0300
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0

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 address@hidden Patch should be based on current GIT master ( 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/" 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.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]