From: John Keeping <john@keeping.me.uk>
Date: Mon, 30 Jun 2014 08:08:29 GMT
Subject: Re: `git log --graph` with multiple roots is confusing
Message-ID: <20140630080829.GB13153@serenity.lan>
In-Reply-To: <CALygMcDXjMUcq=8ERVTES+5qNjLMe_OFPbmeqAosU7qmk=QuUQ@mail.gmail.com>

On Sun, Jun 29, 2014 at 11:40:40PM -0700, Gary Fixler wrote:
> I sometimes pull things in from unrelated repositories to rebase or
> cherry-pick items from a different line of development. I've done this
> to bring isolated features into a project in their own feature
> branches with their full development histories, and also to extract
> lines of development out to their own project, with their histories
> intact. These are usually not connected commits, but things I have to
> track down across time with `git log -S` and friends.
> 
> When I `git remote add otherrepo <url>`, then view things with my
> aliased `git log --oneline --all --graph --decorate` alias, I'm
> usually immediately straining to figure out what's what, as the two
> trees stack onto each other with no separation. It would be nice if
> root commits used something other than *, and/or if they could be
> colored differently by default, or via some option to make them stand
> out as parent-less commits.
> 
> Is this feasible, or already possible?

Have you tried `git log --boundary`?