Git development
 help / color / mirror / Atom feed
From: John Keeping <john@keeping.me.uk>
To: Gary Fixler <gfixler@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: `git log --graph` with multiple roots is confusing
Date: Mon, 30 Jun 2014 09:08:29 +0100	[thread overview]
Message-ID: <20140630080829.GB13153@serenity.lan> (raw)
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`?

  reply	other threads:[~2014-06-30  8:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-30  6:40 `git log --graph` with multiple roots is confusing Gary Fixler
2014-06-30  8:08 ` John Keeping [this message]
2014-06-30 10:04   ` Gary Fixler
2014-07-09  6:51     ` Jeff King
2014-07-09  7:16       ` Duy Nguyen

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=20140630080829.GB13153@serenity.lan \
    --to=john@keeping.me.uk \
    --cc=gfixler@gmail.com \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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