[PATCH v2 2/2] Provide better guidance for submitting patches against upstream utilities
- From
- Jason Holden <jason.k.holden.swdev@gmail.com>
- Date
- Dec 31, 2012, 22:19 UTC
- Message-ID
- <1356992375-11116-3-git-send-email-jason.k.holden.swdev@gmail.com>
- In-Reply-To
- <1356992375-11116-1-git-send-email-jason.k.holden.swdev@gmail.com>
git-gui, gitk, and git-po are maintained upstream of git. Document this, and the procedure for submitting patches to these tools
Signed-off-by: Jason Holden <jason.k.holden.swdev@gmail.com> --- Documentation/SubmittingPatches | 11 +++++++++++ 1 file changed, 11 insertions(+)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches index 75935d5..30b95a8 100644 --- a/Documentation/SubmittingPatches +++ b/Documentation/SubmittingPatches @@ -58,6 +58,17 @@ Checklist (and a short version for the impatient): please test it first by sending email to yourself. - see below for instructions specific to your mailer + Improving upstream utilities (gitk, git-gui, git-po) + - gitk, git-gui, and git-po are maintained upstream of Git + despite being included in Git's git repository + - Patches should be made against the upstream gui repository, + and not against the version in Git's git repository + - The resulting patch should still be emailed for review + to the git mailing list (git@vger.kernel.org), cc'ing the + applicable gui maintainer + - Please see the MAINTAINER's file for the gui maintainer's contact + information and canonical repository location + Long version: I started reading over the SubmittingPatches document for Linux
-- 1.8.1.rc3.28.g0ab5d1f