From: Thell Fowler <git@tbfowler.name>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: Thell Fowler <git@tbfowler.name>,
git@vger.kernel.org, Julian Phillips <julian@quantumfyre.co.uk>
Subject: Re: What's a good setup for submitting patches to the list properly?
Date: Sat, 22 Aug 2009 15:58:43 -0500 (CDT) [thread overview]
Message-ID: <alpine.DEB.2.00.0908221531230.29625@GWPortableVCS> (raw)
In-Reply-To: <200908222220.35354.chriscool@tuxfamily.org>
Christian Couder (chriscool@tuxfamily.org) wrote on Aug 22, 2009:
> On Saturday 22 August 2009, Thell Fowler wrote:
> >
> > > What could I have done/checked before sending to make sure that these
> > > would have posted properly?
>
> Perhaps you could send them to yourself.
>
Yes, I did. They all showed up under the correct thread, but then I
changed how I did it by adding cover-letter to the format-patch options.
BTW - After looking at the headers it looks like the cover letter header
worked just fine, but that the cover letter msg-id changed between when
format-patch created it and when it was sent out causing the reset of the
msgs to not have anything to reference to.
> > No input on this? Perhaps I should've posted to the git user or alpine
> > lists?
>
> It's ok to post this kind of questions on the git mailing list.
>
> There is "git send-email" that is bundled with git. But I use
> git-mail-commits from Julian Philips. I am very happy with it. Thanks
> Julian!
>
I guess I'll setup smtp and try the send-email route, not sure if that
is going to change anything having to do with the In-Reply-To field
and a cover letter or how it shows in the threading.
If that doesn't work then I'll give Julian's mail-commits a whirl.
Thanks for replying Christian!
--
Thell
prev parent reply other threads:[~2009-08-22 21:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 0:09 What's a good setup for submitting patches to the list properly? Thell Fowler
2009-08-22 15:01 ` Thell Fowler
2009-08-22 20:20 ` Christian Couder
2009-08-22 20:56 ` git-mail-commits (Re: What's a good setup for submitting patches to the list properly?) Nicolas Sebrecht
2009-08-23 7:11 ` Christian Couder
2009-08-23 23:05 ` Julian Phillips
2009-08-23 23:41 ` git-mail-commits (Re:What's " Nicolas Sebrecht
2009-08-25 0:06 ` Julian Phillips
2009-08-25 0:14 ` Nicolas Sebrecht
2009-08-22 20:58 ` Thell Fowler [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=alpine.DEB.2.00.0908221531230.29625@GWPortableVCS \
--to=git@tbfowler.name \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=julian@quantumfyre.co.uk \
/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