From: "Luke-Jr" <luke@dashjr•org>
To: Mike Hearn <mike@plan99•net>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Changes for version 0.6 are being pulled into HEAD
Date: Wed, 21 Dec 2011 10:44:53 -0500 [thread overview]
Message-ID: <201112211044.54602.luke@dashjr.org> (raw)
In-Reply-To: <CANEZrP0fNUPLPoSb4m9ASyk-1Y+roArNxWu+AKGOgRQN9Ew1TQ@mail.gmail.com>
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` ?
next prev parent reply other threads:[~2011-12-21 15:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-20 20:49 Gavin Andresen
2011-12-21 1:46 ` Luke-Jr
2011-12-21 10:12 ` Mike Hearn
2011-12-21 15:44 ` Luke-Jr [this message]
2011-12-21 16:45 ` Luke-Jr
2011-12-21 17:12 ` Jeff Garzik
2011-12-21 17:14 ` Luke-Jr
2011-12-21 17:17 ` Jeff Garzik
2011-12-21 17:37 ` Luke-Jr
2011-12-21 10:30 ` Wladimir
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=201112211044.54602.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=mike@plan99$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox