From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Roberto Tyley <roberto.tyley@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH 2/2] Add submitGit patch-submission information
Date: Thu, 14 Apr 2016 22:05:03 -0400 [thread overview]
Message-ID: <20160415020503.GB22112@sigill.intra.peff.net> (raw)
In-Reply-To: <xmqq37qng721.fsf@gitster.mtv.corp.google.com>
On Thu, Apr 14, 2016 at 03:27:18PM -0700, Junio C Hamano wrote:
> > + - Create a pull request on https://github.com/git/git and
> > + use https://submitgit.herokuapp.com/ to send it as a patch series
> > + to the mailing list. Note that the PR is just the place where your
> > + patch is born - discussion of the patch should still take place on
> > + the Git mailing list.
>
> This is a tangent but I am wondering if you can do this _without_
> creating a pull request to that repository. I have a watch on that
> repository and my notification gets unnecessarily large because of
> these pull requests that were made _only_ for submitGit. Can't
> submitGit be taught to take a branch in a repository of the
> submitter as input, (instead of a pull request to that public
> repository)?
Yeah, I have noticed that, too. It creates a lot of noise in my
notification feed (which I process by email), to the point that I'll
probably un-watch git/git.
-Peff
next prev parent reply other threads:[~2016-04-15 2:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-14 22:12 [PATCH 1/2] Partition SubmittingPatches doc into two files Roberto Tyley
2016-04-14 22:12 ` [PATCH 2/2] Add submitGit patch-submission information Roberto Tyley
2016-04-14 22:27 ` Junio C Hamano
2016-04-14 23:03 ` Junio C Hamano
2016-04-15 2:05 ` Jeff King [this message]
2016-04-14 22:16 ` [PATCH 1/2] Partition SubmittingPatches doc into two files 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=20160415020503.GB22112@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=roberto.tyley@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).