From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RdOLv-0001Es-Jj for bitcoin-development@lists.sourceforge.net; Wed, 21 Dec 2011 15:45:11 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1RdOLp-0002Hz-Sy for bitcoin-development@lists.sourceforge.net; Wed, 21 Dec 2011 15:45:11 +0000 Received: from ishibashi.localnet (fl-184-4-160-40.dhcp.embarqhsd.net [184.4.160.40]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id BA508560510; Wed, 21 Dec 2011 15:44:59 +0000 (UTC) From: "Luke-Jr" To: Mike Hearn Date: Wed, 21 Dec 2011 10:44:53 -0500 User-Agent: KMail/1.13.7 (Linux/3.1.4-gentoo; KDE/4.7.3; x86_64; ; ) References: <201112202046.42905.luke@dashjr.org> In-Reply-To: X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583 X-PGP-Key-ID: 665FC11DD53E9583 X-PGP-Keyserver: x-hkp://subkeys.pgp.net MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Message-Id: <201112211044.54602.luke@dashjr.org> X-Spam-Score: -2.4 (--) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -2.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.2 AWL AWL: From: address is in the auto white-list X-Headers-End: 1RdOLp-0002Hz-Sy 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Dec 2011 15:45:11 -0000 On Wednesday, December 21, 2011 5:12:07 AM Mike Hearn wrote: > 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. Not sure what you mean. Maybe `git log --no-merges` ?