Re: What's a good setup for submitting patches to the list properly?
- From
Thell Fowler <git@tbfowler.name>
- Date
- Aug 22, 2009, 20:58 UTC
- Message-ID
- <alpine.DEB.2.00.0908221531230.29625@GWPortableVCS>
- In-Reply-To
- <200908222220.35354.chriscool@tuxfamily.org>
Christian Couder (chriscool@tuxfamily.org) wrote on Aug 22, 2009:
Show 7 quoted lines
> 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.
Show 9 quoted lines
> > 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