From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, Jason Holden <jason.k.holden.swdev@gmail.com>
Subject: Re: [PATCH 0/3] Update SubmittingPatches
Date: Wed, 2 Jan 2013 04:08:03 -0500 [thread overview]
Message-ID: <20130102090803.GC9328@sigill.intra.peff.net> (raw)
In-Reply-To: <1357082695-29713-1-git-send-email-gitster@pobox.com>
On Tue, Jan 01, 2013 at 03:24:52PM -0800, Junio C Hamano wrote:
> The main thing this series wants to do is the second one, but I
> wanted to reduce the clutter in this document while at it.
>
> Junio C Hamano (3):
> SubmittingPatches: who am I and who cares?
> SubmittingPatches: mention subsystems with dedicated repositories
> SubmittingPatches: remove overlong checklist
FWIW, all look reasonable to me. I did not pay close attention to the
earlier discussion on MAINTAINERS, but my first thought on reading it
was "why isn't this stuff just in the SubmittingPatches doc? That's
where I would look for it".
I guess some people might balk at the third one, as the checklist is
supposed to help with a quick and easy start. But I agree with your
commit log message that it isn't short or quick anymore. Of course it
has been a long time since I have needed to read that document. Maybe
people who have used it more recently would have more relevant thoughts.
-Peff
prev parent reply other threads:[~2013-01-02 9:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-01 23:24 [PATCH 0/3] Update SubmittingPatches Junio C Hamano
2013-01-01 23:24 ` [PATCH 1/3] SubmittingPatches: who am I and who cares? Junio C Hamano
2013-01-01 23:24 ` [PATCH 2/3] SubmittingPatches: mention subsystems with dedicated repositories Junio C Hamano
2013-01-02 1:52 ` Jason Holden
2013-01-02 2:14 ` Junio C Hamano
2013-01-02 17:22 ` Junio C Hamano
2013-01-04 20:58 ` [PATCH] SubmittingPatches: Document how to request a patch review tag Jason Holden
2013-01-04 21:47 ` Junio C Hamano
2013-01-06 7:32 ` Michael Haggerty
2013-01-06 9:01 ` Junio C Hamano
2013-01-01 23:24 ` [PATCH 3/3] SubmittingPatches: remove overlong checklist Junio C Hamano
2013-01-02 9:08 ` Jeff King [this message]
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=20130102090803.GC9328@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jason.k.holden.swdev@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.
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).