From: "Uwe Kleine-König" <ukleinek@informatik.uni-freiburg.de>
To: Don Zickus <dzickus@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git log filtering
Date: Wed, 7 Feb 2007 18:01:22 +0100 [thread overview]
Message-ID: <20070207170122.GB18704@informatik.uni-freiburg.de> (raw)
In-Reply-To: <68948ca0702070841m76817d9el7ce2ec69835c50e@mail.gmail.com>
Don Zickus wrote:
> I was curious to know what is the easiest way to filter info inside a
> commit message.
>
> For example say I wanted to find out what patches Joe User has
> submitted to the git project.
> I know I can do something like ' git log |grep -B2 "^Author: Joe User"
What about
git log --author="Joe User"
> ' and it will output the matches and the commit id. However, if I
> wanted to filter on something like "Signed-off-by: Joe User", then it
> is a little harder to dig for the commit id.
>
> Is there a better way of doing this? Or should I accept the fact that
> git wasn't designed to filter info like this very quickly?
>
> I guess what I was looking to do was embed some metadata inside the
> commit message and parse through it at a later time (ie like a
> bugzilla number or something).
>
> Any thoughts/tips/tricks would be helpful.
Maybe:
git log | awk -v sob="Joe User" '$1 == "commit" {commit = $2} /Signed-off-by:/ {if (match($0, sob)) print commit}'
Best regards
Uwe
--
Uwe Kleine-König
http://www.google.com/search?q=2004+in+roman+numerals
next prev parent reply other threads:[~2007-02-07 17:01 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-07 16:41 git log filtering Don Zickus
2007-02-07 16:55 ` Jakub Narebski
2007-02-07 17:01 ` Uwe Kleine-König [this message]
2007-02-07 17:12 ` Johannes Schindelin
2007-02-07 17:12 ` Linus Torvalds
2007-02-07 17:25 ` Johannes Schindelin
[not found] ` <7v64ad7l12.fsf@assigned-by-dhcp.cox.net>
2007-02-07 21:03 ` Linus Torvalds
2007-02-07 21:09 ` Junio C Hamano
2007-02-07 21:53 ` Linus Torvalds
2007-02-08 6:16 ` Jeff King
2007-02-08 18:06 ` Johannes Schindelin
2007-02-08 22:33 ` Jeff King
2007-02-09 0:18 ` Johannes Schindelin
2007-02-09 0:23 ` Shawn O. Pearce
2007-02-09 0:45 ` Johannes Schindelin
2007-02-09 10:15 ` Sergey Vlasov
2007-02-09 1:59 ` Jeff King
2007-02-09 13:13 ` Johannes Schindelin
2007-02-09 13:22 ` Jeff King
2007-02-09 15:02 ` Johannes Schindelin
2007-03-07 17:37 ` pcre performance, was " Johannes Schindelin
2007-03-07 18:03 ` Paolo Bonzini
2007-02-08 1:59 ` Horst H. von Brand
2007-02-07 18:16 ` Linus Torvalds
2007-02-07 19:49 ` Fix "git log -z" behaviour Linus Torvalds
2007-02-07 19:55 ` Junio C Hamano
2007-02-07 22:53 ` Don Zickus
2007-02-07 23:05 ` Linus Torvalds
2007-02-08 22:34 ` Junio C Hamano
2007-02-10 7:32 ` Junio C Hamano
2007-02-10 9:36 ` Junio C Hamano
2007-02-10 17:09 ` Linus Torvalds
2007-02-07 18:19 ` git log filtering Don Zickus
2007-02-07 18:27 ` 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=20070207170122.GB18704@informatik.uni-freiburg.de \
--to=ukleinek@informatik.uni-freiburg.de \
--cc=dzickus@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;
as well as URLs for NNTP newsgroup(s).