Git development
 help / color / mirror / Atom feed
From: Thell Fowler <git@tbfowler.name>
To: git@vger.kernel.org
Subject: What's a good setup for submitting patches to the list properly?
Date: Wed, 19 Aug 2009 19:09:58 -0500 (CDT)	[thread overview]
Message-ID: <alpine.DEB.2.00.0908191849220.2012@GWPortableVCS> (raw)

Sorry for once again.

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

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.

At that point, the msg list looked flat, so I opened Evolution Mail and 
looked at them there, they cascaded properly, so I sent them.  Yet, now, 
looking on gmane each of the patch msgs is a top level post and the cover 
letter correctly posted as a reply to the previous thread.

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

-- 
Thell

             reply	other threads:[~2009-08-20  0:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-20  0:09 Thell Fowler [this message]
2009-08-22 15:01 ` What's a good setup for submitting patches to the list properly? 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     ` What's a good setup for submitting patches to the list properly? Thell Fowler

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.0908191849220.2012@GWPortableVCS \
    --to=git@tbfowler.name \
    --cc=git@vger.kernel.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