From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org, "Scott J. Goldman" <scottjg@github.com>
Subject: Re: [PATCH] archive: add archive.restrictRemote option
Date: Fri, 28 Feb 2014 09:51:42 -0800 [thread overview]
Message-ID: <xmqqa9dbw2fl.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140228090709.GB11709@sigill.intra.peff.net> (Jeff King's message of "Fri, 28 Feb 2014 04:07:09 -0500")
Jeff King <peff@peff.net> writes:
> On Thu, Feb 27, 2014 at 10:37:30AM -0800, Junio C Hamano wrote:
>
>> > Signed-off-by: Jeff King <peff@peff.net>
>>
>> Thanks.
>>
>> Do GitHub people have general aversion against signing off (or
>> sending out, for that matter) their own patches, unless they were
>> already active here before they joined GitHub, by the way?
>
> Mostly it is that I clean up the patches and commit messages before
> sending them out. Michael sends out his own patches because they are
> already perfect by the time I see them. :)
>
> I can certainly get S-O-B from GitHubbers, but my impression of the DCO
> is that it does not matter...
> ... A S-O-B from the
> author would perhaps make it more obvious what happened.
Oh, I was not saying the practice was not legit. It was just that I
expected a bit more from GitHub, a leading company that evangelises
use of Git ;-)
> I was hoping to be vague. If we really want to get into specifics, we
> should probably document the current rules (refnames, and sub-trees of
> refnames). It might be a good thing to document that anyway, though. And
> by doing so, it would become obvious why one would want to set this
> option. I'll see what I can come up with.
Thanks.
prev parent reply other threads:[~2014-02-28 17:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-27 4:05 [PATCH] archive: add archive.restrictRemote option Jeff King
2014-02-27 18:37 ` Junio C Hamano
2014-02-28 9:07 ` Jeff King
2014-02-28 9:56 ` [PATCH v2 0/2] lifting upload-archive restrictions Jeff King
2014-02-28 10:01 ` [PATCH v2 1/2] docs: clarify remote restrictions for git-upload-archive Jeff King
2014-02-28 10:04 ` [PATCH v2 2/2] add uploadarchive.allowUnreachable option Jeff King
2014-02-28 17:54 ` [PATCH v2 0/2] lifting upload-archive restrictions Junio C Hamano
2014-02-28 17:51 ` 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=xmqqa9dbw2fl.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=scottjg@github.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).