From: "Geoffrey Irving" <irving@naml.us>
To: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: caching commit patch-ids for fast git-cherry
Date: Thu, 29 May 2008 10:01:58 -0700 [thread overview]
Message-ID: <7f9d599f0805291001mdbb4b42q6f3a1b79bc9bc4e9@mail.gmail.com> (raw)
I'm planning to use cherry picking to manage long term syncing between
cvs/perforce and git repositories. This means I'll have scripts
running git-cherry between branches with hundreds of uncommon commits,
and I want git-cherry to be much, much, faster.
It looks like I can do this by caching commit->patch-id pairs from
commit_patch_id() in patch-ids.c to a file, say
$GIT_DIR/commit-patch-id-cache. The file would be binary and append
only, and could be blown away if . Any suggestions / concerns before
I write this? Is there any reusable efficient map code for storing
the commit->patch-id map, or should I just mirror the blocked storage
+ binary search used for struct patch_ids?
Thanks,
Geoffrey
next reply other threads:[~2008-05-29 17:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 17:01 Geoffrey Irving [this message]
2008-05-29 17:13 ` caching commit patch-ids for fast git-cherry Johannes Schindelin
2008-05-29 17:34 ` Geoffrey Irving
2008-05-29 22:19 ` Johannes Schindelin
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=7f9d599f0805291001mdbb4b42q6f3a1b79bc9bc4e9@mail.gmail.com \
--to=irving@naml.us \
--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).