From: Jeff King <peff@peff.net>
To: David Kastrup <dak@gnu.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>, git@vger.kernel.org
Subject: Re: Can I have this, pretty please?
Date: Sun, 12 Aug 2007 16:02:58 -0400 [thread overview]
Message-ID: <20070812200258.GA13298@sigill.intra.peff.net> (raw)
In-Reply-To: <85abswo9gf.fsf@lola.goethe.zz>
On Sun, Aug 12, 2007 at 09:10:24PM +0200, David Kastrup wrote:
> I'll probably be able to create a Gnus _backend_ for this sort of
> setup (there are even backends for directory browsing: most files
You can somewhat prototype this by just dumping the commits to an mbox
(sorry for the long lines):
git-log \
--pretty=format:'From %H Mon Sep 17 00:00:00 2001%nFrom: %an <%ae>%nDate: %ad%nSubject: %s%nMessage-ID: <%H@none>%nReferences: %P%n%n%b' \
| perl -pe 's/References: (.*)/"References: " . %join(" ", map { "<" . $_ . "\@none>" } split \/ \/, $1)/e' \
>mbox
Looking at an appreciably large chunk of history means that you will be
very far down in a subthread. mutt, at least, doesn't display this in a
very readable way. But my point is that you are probably better to look
at a couple of different view strategies just by dumping and tweaking
the references relationships (which really only takes about a second for
me on the git.git repository).
Also, have you tried looking at tig (make sure to try a recent version
and use the 'g' command to turn on the graph display)? I think it is
similar to what you are looking for, and I have found it to be very fast
(both in implementation and in usability).
-Peff
next prev parent reply other threads:[~2007-08-12 20:03 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-12 13:23 Can I have this, pretty please? David Kastrup
2007-08-12 14:21 ` Steven Grimm
2007-08-12 16:40 ` David Kastrup
2007-08-12 18:38 ` Linus Torvalds
2007-08-12 18:48 ` Linus Torvalds
2007-08-12 19:28 ` Jon Smirl
2007-08-12 19:45 ` Linus Torvalds
2007-08-12 19:48 ` David Kastrup
2007-08-12 19:29 ` David Kastrup
2007-08-12 19:51 ` Uwe Kleine-König
2007-08-12 20:04 ` David Kastrup
2007-08-12 20:21 ` Linus Torvalds
2007-08-12 19:53 ` Linus Torvalds
2007-08-12 20:10 ` David Kastrup
2007-08-13 0:22 ` Paul Mackerras
2007-08-13 5:49 ` David Kastrup
2007-08-12 19:10 ` David Kastrup
2007-08-12 19:24 ` Linus Torvalds
2007-08-12 19:46 ` David Kastrup
2007-08-12 19:59 ` Linus Torvalds
2007-08-12 20:30 ` David Kastrup
2007-08-12 20:58 ` Govind Salinas
2007-08-12 21:35 ` David Kastrup
2007-08-12 22:17 ` Martin Langhoff
2007-08-12 22:54 ` David Kastrup
2007-08-12 20:02 ` Jeff King [this message]
2007-08-12 20:09 ` Jeff King
2007-08-12 21:51 ` David Kastrup
2007-08-12 23:10 ` Jeff King
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=20070812200258.GA13298@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=dak@gnu.org \
--cc=git@vger.kernel.org \
--cc=torvalds@linux-foundation.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).