Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mh.in.england@gmail.com>) id 1RdJ9m-0004VQ-PI
	for bitcoin-development@lists.sourceforge.net;
	Wed, 21 Dec 2011 10:12:18 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
	designates 74.125.82.175 as permitted sender)
	client-ip=74.125.82.175; envelope-from=mh.in.england@gmail.com;
	helo=mail-we0-f175.google.com; 
Received: from mail-we0-f175.google.com ([74.125.82.175])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1RdJ9i-00031F-1K
	for bitcoin-development@lists.sourceforge.net;
	Wed, 21 Dec 2011 10:12:18 +0000
Received: by werm13 with SMTP id m13so3875063wer.34
	for <bitcoin-development@lists.sourceforge.net>;
	Wed, 21 Dec 2011 02:12:08 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.138.226 with SMTP id a76mr3118961wej.51.1324462327877;
	Wed, 21 Dec 2011 02:12:07 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.216.8.7 with HTTP; Wed, 21 Dec 2011 02:12:07 -0800 (PST)
In-Reply-To: <201112202046.42905.luke@dashjr.org>
References: <CABsx9T3u5onesvWr46ZnKCsYAnxxoLn38PuL6K7RrYqmX8pQHw@mail.gmail.com>
	<201112202046.42905.luke@dashjr.org>
Date: Wed, 21 Dec 2011 11:12:07 +0100
X-Google-Sender-Auth: Eo5BSFkwmo-Sb-osMFaJ5LM-9zY
Message-ID: <CANEZrP0fNUPLPoSb4m9ASyk-1Y+roArNxWu+AKGOgRQN9Ew1TQ@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Luke-Jr <luke@dashjr.org>
Content-Type: multipart/alternative; boundary=0016e6d7ea90924f4404b4976a0e
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(mh.in.england[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1RdJ9i-00031F-1K
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Changes for version 0.6 are being pulled
 into HEAD
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Wed, 21 Dec 2011 10:12:18 -0000

--0016e6d7ea90924f4404b4976a0e
Content-Type: text/plain; charset=UTF-8

Thanks for this summary Luke.

Git does not produce very helpful summaries when every commit is a merge.
Is there a way to fix that? You have to guess what a change does based on
the name of the topic branch currently.

--0016e6d7ea90924f4404b4976a0e
Content-Type: text/html; charset=UTF-8

Thanks for this summary Luke.<div><br></div><div>Git does not produce very helpful summaries when every commit is a merge. Is there a way to fix that? You have to guess what a change does based on the name of the topic branch currently.<br>
</div>

--0016e6d7ea90924f4404b4976a0e--