From: Junio C Hamano <gitster@pobox.com>
To: Robert Dailey <rcdailey.lists@gmail.com>
Cc: Git <git@vger.kernel.org>
Subject: Re: git log for only certain branches
Date: Tue, 08 Apr 2014 12:26:05 -0700 [thread overview]
Message-ID: <xmqqvbuj39o2.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAHd499BSgxZ8EC1qKYRsF0hac6rQAegw9qTOoDjaiuh_UUVEng@mail.gmail.com> (Robert Dailey's message of "Tue, 8 Apr 2014 08:43:45 -0500")
Robert Dailey <rcdailey.lists@gmail.com> writes:
> I have more details about my inquiry on StackOverflow:
> http://stackoverflow.com/questions/22823768/view-git-log-with-merges-for-only-certain-branches
>
> Basically I'd like to know if it is possible to show the graph for
> ONLY branches that I list. The key here is that the graph should also
> show relationships between only those branches that I list. In other
> words, any ancestors that I do not explicitly specify should not be
> rendered in the graph.
>
> I have an insanely huge number of branches in my git repo (we
> transitioned from SVN so we haven't had a chance to clean them up
> yet). As a result, the git log graph I see has literally 10-20
> vertical lines and I have to scroll 20+ pages to follow a line to a
> particular parent branch.
I do not quite get this part (note that it is impolite to ask people
to go to stackoverflow or any external site to answer questions
asked here, but I am making an exception today):
$ git log --oneline --graph origin/master origin/topic1
It will show all branches anyway, even though I've specified I only
want to see two of them.
These should show commits reachable from these two branches,
origin/master and origin/topic1, and nothing else.
$ git log --oneline --graph \
origin/master origin/topic1 \
--not $(git merge-base --all origin/master origin/topic1)
would stop where the histories of these two branches meet (assuming
that you consider that the common ancestors of these two not
interesting when you say "all branches anyway", but these common
ancestors are still part of these two branches ;-).
prev parent reply other threads:[~2014-04-08 19:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-08 13:43 git log for only certain branches Robert Dailey
2014-04-08 17:08 ` Matthieu Moy
2014-04-08 19:15 ` Robert Dailey
2014-04-08 17:18 ` Michal Sojka
2014-04-08 19:26 ` Junio C Hamano [this message]
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=xmqqvbuj39o2.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=rcdailey.lists@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).