From: John Ellson <ellson@research.att.com>
To: git@vger.kernel.org
Subject: Wanted - a file browser interface to git
Date: Tue, 18 Oct 2005 20:58:30 -0400 [thread overview]
Message-ID: <dj45np$e88$1@sea.gmane.org> (raw)
I know that Linus thinks that files are less important than commits, but we are
finding a real need to be able to browse though old versions of files and we
have not yet found an efficient way to do it with git.
An example is: "I know that file xxx contained algorithm yyy at some point in
the past and now I'd like to browse back through the history of xxx to find the
exact details."
I think what I'd like is a file browser on git that:
- can navigate the directory tree, starting by default with the HEAD
tree, but able to browse the state of the tree at any time in the history.
- can select any file from the tree, and then view the state of that file at any
time in its history by stepping forward or back through commits that have
affected that file.
- can view the difference between any pair of states of the file, with
annotations as to the source of the changes.
- can search for a string across the complete history of a file.
- can invoke the users choice of editor on the file.
Neither gitk nor qgit provide tree browsing, so it can be hard to get at a
specific file.
qgit has nice file browser that annotates all changes, but I think I'd prefer a
two panel diff view.
Neither qgit not gitk provide links to an editor so that a file can be worked on
once found.
Am I out in left field here, or does anyone else feel the need for something
like this?
John
next reply other threads:[~2005-10-19 1:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-19 0:58 John Ellson [this message]
2005-10-19 1:07 ` Wanted - a file browser interface to git Linus Torvalds
2005-10-19 1:23 ` John Ellson
2005-10-19 3:03 ` Linus Torvalds
2005-10-19 3:15 ` [PATCH] cg-history FILE [NTH_PARENT] - was: " John Ellson
2005-10-19 4:01 ` [PATCH] cg-history FILE [NTH_PARENT] 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='dj45np$e88$1@sea.gmane.org' \
--to=ellson@research.att.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;
as well as URLs for NNTP newsgroup(s).