From: Kay Sievers <kay.sievers@vrfy.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Linus Torvalds <torvalds@osdl.org>,
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: Fri, 27 May 2005 01:59:44 +0200 [thread overview]
Message-ID: <20050526235944.GB6215@vrfy.org> (raw)
In-Reply-To: <7vy8a18w1e.fsf@assigned-by-dhcp.cox.net>
On Thu, May 26, 2005 at 03:25:17PM -0700, Junio C Hamano wrote:
> >>>>> "KS" == Kay Sievers <kay.sievers@vrfy.org> writes:
>
> KS> Nice, thanks. Here is a very first try. It searches the commit messages
> KS> and uses pickaxe to search in the file content:
> KS> http://ehlo.org/~kay/gitweb.cgi?p=git/git.git;a=search;s=symlink
>
> Nice, thanks for using pickaxe ;-). One request, knowing well
> that what you have on ehlo is your first cut.
Yeah, I like it a lot. Nice work.
Any idea, what's the reason, it doesn't find anything here in the
kernel tree:
git-rev-list HEAD | git-diff-tree -S'TIMEOUT' --stdin
while:
git-rev-list --header HEAD | grep -z TIMEOUT
prints the commit:
6897089c5f7989603ccb9c696050470ba1dbd262
with the following change:
git-diff-tree -p 6897089c5f7989603ccb9c696050470ba1dbd262 6f31e42221c7deae4527136ce0dd73990d8bc1d1
diff --git a/drivers/base/firmware_class.c
b/drivers/base/firmware_class.c
--- a/drivers/base/firmware_class.c
+++ b/drivers/base/firmware_class.c
@@ -102,9 +102,6 @@ firmware_class_hotplug(struct class_devi
if (add_hotplug_env_var(envp, num_envp, &i, buffer, buffer_size, &len,
"FIRMWARE=%s", fw_priv->fw_id))
return -ENOMEM;
- if (add_hotplug_env_var(envp, num_envp, &i, buffer, buffer_size,
&len,
- "TIMEOUT=%i", loading_timeout))
- return -ENOMEM;
envp[i] = NULL;
> The pickaxe really shines when you can paste a couple of lines
> of code in the version you are having trouble with (or just you
> are curious about) in order to see where they came from. For
> example, I did an equivalent of the following command back to
> figure out which patch and author to give credit to when I stole
> the tagged output format for git-ls-files from Cogito branch:
>
> git-rev-list pasky |
> git-diff-tree -v -p --stdin \
> -S'static const char *tag_cached = "";
> static const char *tag_unmerged = "";
> static const char *tag_removed = "";'
Nice feature, maybe we can add it later (see next).
> Since this is primarily about program code, forbidding '*' is
> rather nasty, and not being able to do multiple lines makes it
> quite less useful than it could be.
I see what you mean, but allow to pass any charater through a cgi to a
invoked shell as a command-line option is a nightmare without being very
carful. That's why only a few character allowed now. I'm not sure how
to do that without creating possibly a big hole in the webserver. :)
Kay
next prev parent reply other threads:[~2005-05-26 23:58 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
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 [this message]
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=20050526235944.GB6215@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).