All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>
To: Julian Phillips <julian@quantumfyre.co.uk>
Cc: Christian Couder <chriscool@tuxfamily.org>,
	Nicolas Sebrecht <nicolas.s.dev@gmx.fr>,
	Thell Fowler <git@tbfowler.name>,
	git@vger.kernel.org
Subject: Re: git-mail-commits (Re:What's a good setup for submitting patches to the list properly?)
Date: Mon, 24 Aug 2009 01:41:08 +0200	[thread overview]
Message-ID: <20090823234108.GB3526@vidovic> (raw)
In-Reply-To: <alpine.LNX.2.00.0908232357590.15613@reaper.quantumfyre.co.uk>

The 24/08/09, Julian Phillips wrote:
> On Sun, 23 Aug 2009, Christian Couder wrote:
>
> Using the awsome power of git I have managed to extract it from my random 
> tools private repo to here as if I had written it to be a separate entity 
> from the start:
>
> git://git.q42.co.uk/mail_commits.git
> (gitweb: http://git.q42.co.uk/w/mail_commits.git)

Thanks a lot.

> If it would be considered useful, then I can also create a patch to add 
> it to contrib 

I think it worth. That said, I would first add some config options like
mail-commits.cc (not reviewed that much yet) to be a bit more consistent
with the send-email program. I would also add README and INSTALL files.

Could you please consider to place your code under GPLv2?

-- 
Nicolas Sebrecht

  reply	other threads:[~2009-08-23 23:41 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           ` Nicolas Sebrecht [this message]
2009-08-25  0:06             ` git-mail-commits (Re:What's " 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=20090823234108.GB3526@vidovic \
    --to=nicolas.s.dev@gmx.fr \
    --cc=chriscool@tuxfamily.org \
    --cc=git@tbfowler.name \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.