git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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

From
Christian Couder <chriscool@tuxfamily.org>
Date
Aug 22, 2009, 20:20 UTC
Message-ID
<200908222220.35354.chriscool@tuxfamily.org>
In-Reply-To
<alpine.DEB.2.00.0908220953460.2012@GWPortableVCS>
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.
> 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!

Regards, Christian.

Previous: Thell FowlerNext: Nicolas Sebrecht
Message 3 of 10 in “What's a good setup for submitting patches to the list properly?”
  1. Thell FowlerAug 20, 2009
  2. Thell FowlerAug 22, 2009
  3. Christian CouderAug 22, 2009
  4. git-mail-commits (Re: What's a good setup for submitting patches to the list properly?)Nicolas Sebrecht, Aug 22, 2009
  5. Christian CouderAug 23, 2009
  6. Julian PhillipsAug 23, 2009
  7. Nicolas SebrechtAug 23, 2009
  8. Julian PhillipsAug 25, 2009
  9. Nicolas SebrechtAug 25, 2009
  10. Thell FowlerAug 22, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.