From: Jason Holden <jason.k.holden.swdev@gmail.com>
To: git@vger.kernel.org
Cc: gitster@pobox.com, th.acker@arcor.de, paulus@samba.org,
patthoyts@users.sourceforge.net, worldhello.net@gmail.com,
Jason Holden <jason.k.holden.swdev@gmail.com>
Subject: [PATCH v2 2/2] Provide better guidance for submitting patches against upstream utilities
Date: Mon, 31 Dec 2012 17:19:35 -0500 [thread overview]
Message-ID: <1356992375-11116-3-git-send-email-jason.k.holden.swdev@gmail.com> (raw)
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
next prev parent reply other threads:[~2012-12-31 22:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-31 22:19 [PATCH v2 0/2] Add MAINTAINERS file and clarify gui workflows Jason Holden
2012-12-31 22:19 ` [PATCH v2 1/2] Add top-level maintainers file with email/canonical repository information Jason Holden
2012-12-31 22:25 ` Jacob Helwig
2012-12-31 22:19 ` Jason Holden [this message]
2012-12-31 23:39 ` [PATCH v2 2/2] Provide better guidance for submitting patches against upstream utilities Junio C Hamano
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1356992375-11116-3-git-send-email-jason.k.holden.swdev@gmail.com \
--to=jason.k.holden.swdev@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=patthoyts@users.sourceforge.net \
--cc=paulus@samba.org \
--cc=th.acker@arcor.de \
--cc=worldhello.net@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).