From: "Marco Costalba" <mcostalba@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Subject: qgit: Annotate hundreds of files at terrific speed ;-)
Date: Sat, 23 Jun 2007 18:35:11 +0200 [thread overview]
Message-ID: <e5bfff550706230935m5363a6dava9dbd62a56a1b685@mail.gmail.com> (raw)
- pull from git://git.kernel.org/pub/scm/qgit/qgit4.git
- compile + install
- run qgit on the git repo
- select the 900 pounds gorilla called 'Makefile' from tree view ('t'
key shortcut)
- double click on it so to start file viewer and annotation
- say wahooo!
You get _all_ the hundreds (more then 800) of revisions of this
monster history annotated in the time it takes *other* ;-) tools to
annotate just one of them.
Ok. Come back to earth. I've just pushed some patches to use 'git log'
instead of 'git rev-list' as interface with git.
By using git-log with '-p' option it is possible to get a file history
_and_ corresponding diff in one pass instead of the double step
git-rev-list + git-diff-tree. Speed up it's huge.
But there are other gains:
- qgit can now be run with any command line argument known to 'git log'
- when Linus patch 'git log --follow' will be accepted by Junio the
following of file renames will come automatically
Unfortunately there are issues too:
- git-log lacks currently a --stdin option needed to pass a long list
of sha's, something that a tool sometime wants to do.
- because of the previous issue a StGIT repo under with a long list of
unapplied patches may break 'git log' loading.
- probably 'git log --follow' will come semi-automatically because an
incompatibility with '--parents' option, as pointed out by Linus,
needs a workaround. The latter is currently used to handle the grafts.
Marco
next reply other threads:[~2007-06-23 16:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-23 16:35 Marco Costalba [this message]
2007-06-24 23:08 ` qgit: Annotate hundreds of files at terrific speed ;-) Shawn O. Pearce
2007-06-25 5:59 ` Marco Costalba
2007-06-25 6:35 ` Nanako Shiraishi
[not found] ` <200706250638.l5P6crkS026564@mi1.bluebottle.com>
2007-06-25 11:20 ` Marco Costalba
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=e5bfff550706230935m5363a6dava9dbd62a56a1b685@mail.gmail.com \
--to=mcostalba@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