From: Jakub Narebski <jnareb@gmail.com>
To: Josef Wolf <jw@raven.inka.de>
Cc: git@vger.kernel.org
Subject: Re: How to restrict gitk to show only branch/merge commits?
Date: Wed, 06 May 2009 00:51:16 -0700 (PDT) [thread overview]
Message-ID: <m37i0uoej7.fsf@localhost.localdomain> (raw)
In-Reply-To: <20090506072053.GL15420@raven.wolf.lan>
Josef Wolf <jw@raven.inka.de> writes:
> I would like gitk to show me only the heads, branch-points and
> merge-points of branches.
>
> For example, given a history like this:
>
> d...e--F--g...h--H
> / \
> a1--a2...an--b--C N--o...p--P
> \ /
> i...j--K--l...m--M
>
> I would like to see only
>
> - a1 because it has no parent
> - C,F,K because they are reachable from multiple heads
> - N because it has multiple parents
> - H,M,P because they are heads
>
> Ideally, there would be a possibility to add some "context" to the
> list of commits to be shown: with $context==1, all the commits shown
> in the above history would be shown, but the commits indicated by
> the triple-dots would be omitted.
>
> The reason is that I have some repositories with several really long
> linear history. It is hard to get a global overview about the branch
> history if you have to scroll constantly.
>
> Is something like that possible with gitk?
I am not sure if it would give you exactly what you want, but if I
understand correctly gitk accepts arguments for git-log (and you can
set them somewhere in options, too). Take a look at section "History
Simplification" in git-log/git-rev-list manpage, in particular at
option '--simplify-by-decoration' there.
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2009-05-06 7:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 7:20 How to restrict gitk to show only branch/merge commits? Josef Wolf
2009-05-06 7:42 ` Andreas Ericsson
2009-05-06 7:51 ` Jakub Narebski [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=m37i0uoej7.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=jw@raven.inka.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.