All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joshua Jensen <jjensen@workspacewhiz.com>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Quickly searching for a note
Date: Fri, 21 Sep 2012 08:41:04 -0600	[thread overview]
Message-ID: <505C7C80.3000700@workspacewhiz.com> (raw)

Background: To tie Perforce changelists to Git commits, I add a note to 
a commit with the form "P4@123456".  Later, I use the note to sync down 
the closest Perforce changelist matching the Git commit.

I search for these notes by getting a list of revisions:

         git rev-list --max-count=1000

I iterate those revisions and run git show and grep on each:

         git show -s --format=%N%n%s --show-notes=p4notes COMMIT

For short runs, this isn't so bad.  For longer runs of commits (I just 
walked through approximately 100), it takes a long time. Running 'git 
show' is costing me about 7/10 of second, presumably because I am on 
Windows.

Is there a faster way to do this?

Thanks.

Josh

             reply	other threads:[~2012-09-21 14:47 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21 14:41 Joshua Jensen [this message]
2012-09-21 15:10 ` Quickly searching for a note Andreas Schwab
2012-09-21 18:34   ` Joshua Jensen
2012-09-21 17:21 ` Junio C Hamano
2012-09-21 18:29   ` Joshua Jensen
2012-09-21 20:04     ` Junio C Hamano
2012-09-21 20:25       ` Joshua Jensen
2012-09-21 20:50         ` Johannes Sixt
2012-09-21 21:10           ` Joshua Jensen
2012-09-21 23:37             ` Jeff King
2012-09-21 23:51               ` Junio C Hamano
2012-09-22 16:10                 ` Michael J Gruber
2012-09-22 20:23                   ` Junio C Hamano
2012-09-23 15:07                     ` Michael J Gruber
2012-09-25  0:42                       ` Jeff King
2012-09-25  7:24                         ` Michael J Gruber
2012-09-25  0:38                     ` Jeff King
2012-09-25 16:19                       ` Junio C Hamano
2012-09-22  4:51 ` 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=505C7C80.3000700@workspacewhiz.com \
    --to=jjensen@workspacewhiz.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.