From: Ryan Anderson <ryan@michonline.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH] Add SubmittingPatches
Date: Mon, 15 Aug 2005 23:28:11 -0400 [thread overview]
Message-ID: <20050816032811.GI7001@mythryan2.michonline.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0508160335420.1574@wgmdd8.biozentrum.uni-wuerzburg.de>
On Tue, Aug 16, 2005 at 03:41:04AM +0200, Johannes Schindelin wrote:
> On Mon, 15 Aug 2005, Junio C Hamano wrote:
>
> > Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> >
> > > Maybe we should enhance git-applymbox to detect whitespace corruption in
> > > particular, and output the User-Agent header (or if that does not
> > > exist, the Message-ID header; thanks, pine) on error.
> >
>
> Alternatively, SubmittingPatches could include a big fat CAVEAT, and a
> note that the submitter might want to send a single SP to herself, save
> the received mail and check that all is well, prior to sending the first
> patch. I mean, well, erm, it is sort of, uh, annoying, to send out a
> corrupt patch *speaksofyourstruly*.
If you have some trouble sending them out, you can use
git format-patch --mbox
and
git send-email
which seems to consistently do the right thing.
--
Ryan Anderson
sometimes Pug Majere
next prev parent reply other threads:[~2005-08-16 3:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-13 9:08 [PATCH] Add SubmittingPatches Junio C Hamano
2005-08-15 23:50 ` Johannes Schindelin
2005-08-16 0:24 ` Linus Torvalds
2005-08-16 0:37 ` Junio C Hamano
2005-08-16 1:03 ` Johannes Schindelin
2005-08-16 1:23 ` Junio C Hamano
2005-08-16 1:41 ` Johannes Schindelin
2005-08-16 3:28 ` Ryan Anderson [this message]
2005-08-16 15:22 ` Submitting patches w/ Thunderbird [was: Re: [PATCH] Add SubmittingPatches] A Large Angry SCM
2005-08-16 0:25 ` [PATCH] Add SubmittingPatches 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=20050816032811.GI7001@mythryan2.michonline.com \
--to=ryan@michonline.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).