From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <gitster@pobox.com>, paulus@samba.org
Cc: git@vger.kernel.org
Subject: [PATCH] Point out merged submodule maintainers as better addresses for patches
Date: Wed, 26 Dec 2007 23:12:20 -0500 [thread overview]
Message-ID: <20071227041220.GA22256@spearce.org> (raw)
Junio doesn't directly manage the git-gui or gitk-git subdirectories
within git.git; these are currently managed by other individuals
and then periodically merged to git.git. Users often send patches
to Junio for these directories when they should be directed at the
current maintainer instead, so we should point out these special
cases in the SubmittingPatches documentation.
Signed-off-by: Shawn O. Pearce <spearce@spearce.org>
---
Just a suggestion. Might help people who are new to the Git
community to get involved.
Documentation/SubmittingPatches | 8 +++++++-
1 files changed, 7 insertions(+), 1 deletions(-)
diff --git a/Documentation/SubmittingPatches b/Documentation/SubmittingPatches
index de08d09..b7c886c 100644
--- a/Documentation/SubmittingPatches
+++ b/Documentation/SubmittingPatches
@@ -34,10 +34,16 @@ Checklist (and a short version for the impatient):
- if your name is not writable in ASCII, make sure that
you send off a message in the correct encoding.
- send the patch to the list (git@vger.kernel.org) and the
- maintainer (gitster@pobox.com). If you use
+ active maintainer (see below). If you use
git-send-email(1), please test it first by sending
email to yourself.
+ Active maintainers:
+
+ - git-gui/ submodule: spearce@spearce.org
+ - gitk-git/ submodule: paulus@samba.org
+ - Everything else: gitster@pobox.com
+
Long version:
I started reading over the SubmittingPatches document for Linux
--
1.5.4.rc2.1097.gb6e0d
next reply other threads:[~2007-12-27 4:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-27 4:12 Shawn O. Pearce [this message]
2007-12-27 4:37 ` [PATCH] Point out merged submodule maintainers as better addresses for patches 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20071227041220.GA22256@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=paulus@samba.org \
/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.
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 NNTP newsgroup(s).