From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1LwgtC-0007ei-38
	for qemu-devel@nongnu.org; Wed, 22 Apr 2009 14:09:42 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1Lwgt7-0007e5-61
	for qemu-devel@nongnu.org; Wed, 22 Apr 2009 14:09:41 -0400
Received: from [199.232.76.173] (port=39561 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1Lwgt7-0007e2-0w
	for qemu-devel@nongnu.org; Wed, 22 Apr 2009 14:09:37 -0400
Received: from mail2.shareable.org ([80.68.89.115]:46055)
	by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32)
	(Exim 4.60) (envelope-from <jamie@shareable.org>) id 1Lwgt6-0002Fg-Jj
	for qemu-devel@nongnu.org; Wed, 22 Apr 2009 14:09:36 -0400
Date: Wed, 22 Apr 2009 19:09:33 +0100
From: Jamie Lokier <jamie@shareable.org>
Subject: Re: [Qemu-devel] Switching to git
Message-ID: <20090422180932.GA11616@shareable.org>
References: <49EF1A26.70007@us.ibm.com>
	<761ea48b0904220720h48a3c53cv9f90a3c94a31f5d5@mail.gmail.com>
	<49EF282C.8010602@us.ibm.com>
	<0240830B-5527-4567-B605-51C173C39239@web.de>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <0240830B-5527-4567-B605-51C173C39239@web.de>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Andreas =?iso-8859-1?Q?F=E4rber?= <andreas.faerber@web.de>
Cc: qemu-devel <qemu-devel@nongnu.org>

Andreas Färber wrote:
> Unfortunately tools like git-send-email make me loose information  
> instead, by not saving the sent patches in my mail client's or IMAP  
> server's Sent Mail folder...

This can be done.  Looking briefly at git-send-email's man page, The
--bcc= option (which can be put in a config file) could be used to
send yourself copies on a special address
("user+git-sent@mydomain.com") which you store in your sent folder
using a procmail filter or similar.  That's the most versatile option
- it should work with any mail system which has filtering rules.

Or you could use the --smtp-server= option to send the mail via a
script of your choice which stores a copy.  I wouldn't be surprised if
the script could just run "mutt -H" to send the mail in a usual way.

-- Jamie