From: Kay Sievers <kay.sievers@vrfy.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Junio C Hamano <junkio@cox.net>,
pasky@ucw.cz, braddr@puremagic.com, nico@cam.org,
david@dgreaves.com, Git Mailing List <git@vger.kernel.org>
Subject: Re: Summary of core GIT while you are away.
Date: Thu, 26 May 2005 02:44:11 +0200 [thread overview]
Message-ID: <20050526004411.GA12360@vrfy.org> (raw)
In-Reply-To: <Pine.LNX.4.58.0505160837080.28162@ppc970.osdl.org>
On Mon, May 16, 2005 at 09:10:10AM -0700, Linus Torvalds wrote:
>
> The only thing I personally
> think sucks is the author/committer matching of git-rev-list/tree, since
> it would seem like somebody might well like to match on an arbitrary part
> of a commit, and special-casing author/committer seems somewhat broken.
> I personally suspect that both git-rev-list and git-rev-tree should have
> an alternate output format that could be more easily grepped by subsequent
> commands. For example, right now git-rev-list just outputs a list of
> commit ID's, and it might make sense to have a flag to just append the
> commit message to the output, and zero-terminate it (and if the commit
> message has a NUL byte in it, just truncate it at that point).
>
> Then you could just do
>
> git-rev-list -v --header HEAD | grep -z 'author[^\n]*Linus'
>
> to tell it to do the "verbose" thing (only showing the header of the
> commit, not the whole message), and grep for "Linus" in the author line.
What happened to that idea? That's not already working in some other way I
missed, right? The pickaxe stuff is nice and was easy to call from the cgi,
but searching in commit messages would be nice too.
If it's not going to happen in the git-binaries, I may do it just in the
cgi itself.
Kay
next prev parent reply other threads:[~2005-05-26 0:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-14 10:51 Summary of core GIT while you are away Junio C Hamano
2005-05-16 16:10 ` Linus Torvalds
2005-05-16 21:33 ` rev-list/tree committer/author information Junio C Hamano
2005-05-16 22:19 ` Petr Baudis
2005-05-16 22:35 ` Daniel Barkalow
2005-05-16 23:17 ` Junio C Hamano
2005-05-16 22:22 ` Summary of core GIT while you are away Petr Baudis
2005-05-26 0:44 ` Kay Sievers [this message]
2005-05-26 1:13 ` Junio C Hamano
2005-05-26 1:53 ` Linus Torvalds
2005-05-26 1:45 ` Linus Torvalds
2005-05-26 20:27 ` Kay Sievers
2005-05-26 20:51 ` Junio C Hamano
2005-05-26 23:29 ` Kay Sievers
2005-05-26 23:59 ` Junio C Hamano
2005-05-27 1:50 ` H. Peter Anvin
2005-05-27 3:36 ` Junio C Hamano
2005-05-27 4:01 ` H. Peter Anvin
2005-05-27 4:12 ` Junio C Hamano
2005-05-27 4:13 ` H. Peter Anvin
2005-05-27 4:31 ` Junio C Hamano
2005-05-27 5:21 ` Linus Torvalds
2005-05-26 22:11 ` H. Peter Anvin
2005-05-26 22:25 ` Junio C Hamano
2005-05-26 23:59 ` Kay Sievers
2005-05-27 0:16 ` Junio C Hamano
2005-05-27 0:22 ` Kay Sievers
2005-05-27 0:40 ` Junio C Hamano
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=20050526004411.GA12360@vrfy.org \
--to=kay.sievers@vrfy.org \
--cc=braddr@puremagic.com \
--cc=david@dgreaves.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=nico@cam.org \
--cc=pasky@ucw.cz \
--cc=torvalds@osdl.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).