From: Jeff Garzik <jgarzik@pobox.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [RFC] git email submissions
Date: Wed, 16 Nov 2005 13:01:06 -0500 [thread overview]
Message-ID: <437B73E2.3080903@pobox.com> (raw)
In-Reply-To: <437B7213.2020406@zytor.com>
H. Peter Anvin wrote:
> Linus Torvalds wrote:
>
>>
>> On Wed, 16 Nov 2005, Jeff Garzik wrote:
>>
>>> For people without _any_ hosting, it would be nice to give them a
>>> method to
>>> submit some git changes via email.
>>
>>
>> Well, as long as you don't expect me to take those things..
>>
>> BK had it with "bk send"/"bk receive", I used it a couple of times and
>> refuse to do it again.
>>
>
> Personally I think it would be nice if you could do an augmented
> patchset so that the end result is the same (with the same SHA1 IDs) as
> if one had merged a pull, while still being a human-readable patchset.
> The advantage with that is that once merged it'll do the right thing on
> the author's end. I think that's pretty much my answer to Jeff's
> question :)
Agreed.
Though as a disclaimer to Linus and others, I don't plan to use this in
my own submissions to Linus. Just thinking it would be a nice thing to
have, because there are definitely users out there who don't (for
whatever reason) have git-capable hosting.
I would presume an email body would look like
overall description of changes
git log master..HEAD | git shortlog
git diff master..HEAD | diffstat -p1
git diff master..HEAD
<pack file MIME attachment>
Smarter programs would send the overall description and pack file as
"[patch 0/N]", and then post the for-review patches in separate emails
as "[patch M/N]".
Jeff
next prev parent reply other threads:[~2005-11-16 18:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 14:38 [RFC] git email submissions Jeff Garzik
2005-11-16 14:51 ` Petr Baudis
2005-11-16 16:59 ` Linus Torvalds
2005-11-16 17:53 ` H. Peter Anvin
2005-11-16 18:01 ` Jeff Garzik [this message]
2005-11-16 23:20 ` Matthias Urlichs
2005-11-19 21:08 ` Junio C Hamano
2005-11-17 0:38 ` Martin Langhoff
2005-11-17 2:49 ` H. Peter Anvin
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=437B73E2.3080903@pobox.com \
--to=jgarzik@pobox.com \
--cc=git@vger.kernel.org \
--cc=hpa@zytor.com \
--cc=torvalds@osdl.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).