From: Junio C Hamano <gitster@pobox.com>
To: Jens Lehmann <Jens.Lehmann@web.de>
Cc: Tom Freudenberg <th.freudenberg@googlemail.com>,
git@vger.kernel.org, Heiko Voigt <hvoigt@hvoigt.net>,
"W. Trevor King" <wking@tremily.us>
Subject: Re: Feedback on submitting patches / here submodule
Date: Sun, 09 Nov 2014 09:38:47 -0800 [thread overview]
Message-ID: <xmqqtx28clzs.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <545F955A.1050700@web.de> (Jens Lehmann's message of "Sun, 09 Nov 2014 17:24:58 +0100")
Jens Lehmann <Jens.Lehmann@web.de> writes:
> A patch should go to: gitster@pobox.com /and/ cc: git@vger.kernel.org
> (and optinally any people relevant to the area you are touching).
No. A patch should go To: git@vger.kernel.org and Cc: those who are
involved in the area, and after those involved in the area agree
that it is a good change, please Cc: me with acks from them.
For submodule patches, I am unlikely to be on the To: or Cc: list of
the initial proposal.
prev parent reply other threads:[~2014-11-09 17:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-09 11:39 Feedback on submitting patches / here submodule Tom Freudenberg
2014-11-09 16:24 ` Jens Lehmann
2014-11-09 17:38 ` Junio C Hamano [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=xmqqtx28clzs.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=hvoigt@hvoigt.net \
--cc=th.freudenberg@googlemail.com \
--cc=wking@tremily.us \
/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).