Re: What's a good setup for submitting patches to the list properly?

From: Thell Fowler <git@tbfowler.name>
Date: Aug 22, 2009, 15:01 UTC
Message-ID: <alpine.DEB.2.00.0908220953460.2012@GWPortableVCS>
In-Reply-To: <alpine.DEB.2.00.0908191849220.2012@GWPortableVCS>

Thell Fowler (git@tbfowler.name) wrote on Aug 19, 2009:

Show 13 quoted lines

> I haven't been able to figure out a good setup for posting patches to the 
> list correctly, perhaps someone could tell me where I'm going wrong.
> 
> Alpine is setup to access git @ tbfowler.name with the 'postpone' folder 
> being the 'Drafts' folder on the remote mail host, and a local mbox folder 
> ~/mail/git
> 
> Locally I prepped the emails using:
> 
> git format-patch --cover-letter --full-index -n 
> --in-reply-to=1249428804.2774.52.camel@GWPortableVCS --thread --signoff -6 
> --stdout>>~/mail/git
>

Did I miss something with that command?

Show 8 quoted lines

> http://article.gmane.org/gmane.comp.version-control.git/124834
> 
> Thinking that the cover letter would be in reply to a previous thread, and 
> that the rest would show as a reply to that.  After doing the 
> format-patch, I went into Alpine's git folder selected the messages and 
> saved them to the Drafts folder, then did 'compose' for each one, filling 
> in the information I thought was needed.
>

Perhaps the saving to a new folder could've messed something up with the headers?

[snip]

> What could I have done/checked before sending to make sure that these 
> would have posted properly?

No input on this? Perhaps I should've posted to the git user or alpine lists?

Either way, I'll be sending a new version of the patch I've been working on and rather than have them show as top posts again I'd rather do it correctly.

Or perhaps there is an easier more direct route...

-- 
Thell