From: Jonathan Nieder <jrnieder@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Christian Couder <chriscool@tuxfamily.org>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [RFC/PATCH 2/4] revert: refactor code into a do_pick_commit() function
Date: Sun, 30 May 2010 15:07:08 -0500 [thread overview]
Message-ID: <20100530200708.GA32728@progeny.tock> (raw)
In-Reply-To: <AANLkTik6SBEkOICHdMYprzGitfS2hezDXKQ8Q5R8cAYs@mail.gmail.com>
Ramkumar Ramachandra wrote:
> Christian Couder wrote:
>> -static int revert_or_cherry_pick(int argc, const char **argv)
>> +static int do_pick_commit()
>> {
>> unsigned char head[20];
>> struct commit *base, *next, *parent;
>
> Is there a better way to do this instead of allocating memory for each
> commit? When you cherry pick a lot of commits, it might make sense to
> use a shared memory pool.
In fact they do belong to a pool, as far as I can tell.
lookup_commit_reference ->
lookup_commit_reference_gently ->
parse_object ->
parse_object_buffer ->
lookup_commit ->
lookup_object (or create_object, alloc_commit_node)
alloc_commit_node is defined in alloc.c to draw from a growing array
of fixed-size, never-freed commit objects.
Hope that helps.
Jonathan
next prev parent reply other threads:[~2010-05-30 20:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 4:40 [RFC/PATCH 0/4] implement "git cherry-pick A..B" Christian Couder
2010-05-29 4:40 ` [RFC/PATCH 1/4] revert: use run_command_v_opt() instead of execv_git_cmd() Christian Couder
2010-05-29 4:40 ` [RFC/PATCH 2/4] revert: refactor code into a do_pick_commit() function Christian Couder
2010-05-30 11:19 ` Ramkumar Ramachandra
2010-05-30 20:07 ` Jonathan Nieder [this message]
2010-05-30 20:29 ` Christian Couder
2010-05-29 4:40 ` [RFC/PATCH 3/4] revert: allow cherry-picking a range of commits Christian Couder
2010-05-29 15:27 ` Junio C Hamano
2010-05-30 6:41 ` Christian Couder
2010-05-29 15:47 ` Johannes Schindelin
2010-05-30 6:45 ` Christian Couder
2010-06-01 3:12 ` Christian Couder
2010-05-29 4:40 ` [RFC/PATCH 4/4] revert: add tests to check " Christian Couder
2010-05-29 13:12 ` [RFC/PATCH 0/4] implement "git cherry-pick A..B" Sverre Rabbelier
2010-05-30 7:41 ` Christian Couder
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=20100530200708.GA32728@progeny.tock \
--to=jrnieder@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=artagnon@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.