From: Paul Mackerras <paulus@samba.org>
To: git@vger.kernel.org
Subject: new gitk feature
Date: Wed, 26 Apr 2006 20:59:29 +1000 [thread overview]
Message-ID: <17487.21137.344427.173131@cargo.ozlabs.ibm.com> (raw)
I just pushed some changes to gitk which add a new feature, the
ability to have multiple "views" of a repository. Each view is a
subgraph of the full graph. At the moment the only subgraph that you
can specify is the subgraph containing the commits that affect a
specified set of files or directories. You can switch between views
quickly, and if the currently selected commit exists in the new view
when you switch views, it is selected in the new view. There is one
view which always exists, the "All files" view. If files or
directories are specified on the command line, a "Command line" view
is automatically created and selected at startup.
Thus, for the kernel repository I can have a "PPC" view which shows
changes to arch/powerpc, include/asm-powerpc etc. When looking at a
commit in that view, I can switch to the "All files" view to see where
that commit fits in the overall history.
There is a "View" menu which contains the menu items for creating,
deleting, editing and selecting views. If you check the "Remember
this view" box, gitk will write the definition of the view to your
~/.gitk file, and it will be automatically put in the list on startup.
I plan to add various other kinds of views, for example, a view that
shows only the commits that affect a selected file (or part of a file,
perhaps), and a view that shows just the current commit together with
all the commits that have tags. (The latter will require some help
from git-rev-list. :)
Paul.
next reply other threads:[~2006-04-26 10:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-26 10:59 Paul Mackerras [this message]
2006-04-26 13:57 ` new gitk feature Jan-Benedict Glaw
2006-04-26 15:09 ` Linus Torvalds
2006-04-27 23:52 ` Paul Mackerras
2006-04-28 5:11 ` Linus Torvalds
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=17487.21137.344427.173131@cargo.ozlabs.ibm.com \
--to=paulus@samba.org \
--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;
as well as URLs for NNTP newsgroup(s).