From: Jonathan Nieder <jrnieder@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Christian Couder <chriscool@tuxfamily.org>,
git@vger.kernel.org,
Linus Torvalds <torvalds@linux-foundation.org>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Stephan Beyer <s-beyer@gmx.net>,
Daniel Barkalow <barkalow@iabervon.org>,
Paolo Bonzini <bonzini@gnu.org>,
Stephen Boyd <bebarino@gmail.com>
Subject: Re: [PATCH 3/6] revert: add --ff option to allow fast forward when cherry-picking
Date: Sat, 20 Mar 2010 21:01:20 -0500 [thread overview]
Message-ID: <20100321020120.GA30915@progeny.tock> (raw)
In-Reply-To: <7vhbowoj8y.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> diff --git a/builtin-revert.c b/builtin-revert.c
> index eff5268..bfe75c8 100644
> --- a/builtin-revert.c
> +++ b/builtin-revert.c
> @@ -314,6 +346,10 @@ static int revert_or_cherry_pick(int argc, const char **argv)
> else
> parent = commit->parents->item;
>
> + if (action == CHERRY_PICK && allow_ff
> + && !hashcmp(parent->object.sha1, head))
> + return fast_forward_to(commit->object.sha1, head);
> +
> if (!(message = commit->buffer))
> die ("Cannot get commit message for %s",
> sha1_to_hex(commit->object.sha1));
Here’s a small fix to go on top.
-- %< --
Subject: revert: fix tiny memory leak in cherry-pick --ff
We forgot to free defmsg when returning early for a fast-forward.
Fixing this should reduce noise during test suite runs with valgrind.
More importantly, once cherry-pick learns to pick multiple commits,
the amount of memory leaked would start to add up.
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
---
builtin-revert.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
diff --git a/builtin-revert.c b/builtin-revert.c
index 476f41e..9a3c14c 100644
--- a/builtin-revert.c
+++ b/builtin-revert.c
@@ -274,7 +274,7 @@ static int revert_or_cherry_pick(int argc, const char **argv)
int i, index_fd, clean;
char *oneline, *reencoded_message = NULL;
const char *message, *encoding;
- char *defmsg = git_pathdup("MERGE_MSG");
+ char *defmsg = NULL;
struct merge_options o;
struct tree *result, *next_tree, *base_tree, *head_tree;
static struct lock_file index_lock;
@@ -364,6 +364,7 @@ static int revert_or_cherry_pick(int argc, const char **argv)
* reverse of it if we are revert.
*/
+ defmsg = git_pathdup("MERGE_MSG");
msg_fd = hold_lock_file_for_update(&msg_file, defmsg,
LOCK_DIE_ON_ERROR);
--
1.7.0.2
next prev parent reply other threads:[~2010-03-21 2:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 22:21 [PATCH v2 00/12] add --ff option to cherry-pick Christian Couder
2010-02-28 22:21 ` [PATCH v2 01/12] revert: libify cherry-pick and revert functionnality Christian Couder
2010-02-28 22:21 ` [PATCH v2 02/12] pick: refactor checking parent in a check_parent function Christian Couder
2010-02-28 22:21 ` [PATCH v2 03/12] pick: make check_parent function extern Christian Couder
2010-02-28 22:21 ` [PATCH v2 04/12] pick: move calling check_parent() ouside pick_commit() Christian Couder
2010-02-28 22:22 ` [PATCH v2 05/12] reset: refactor updating heads into a static function Christian Couder
2010-02-28 22:22 ` [PATCH v2 06/12] reset: refactor reseting in its own function Christian Couder
2010-02-28 22:22 ` [PATCH v2 07/12] reset: make reset function non static and declare it in "reset.h" Christian Couder
2010-02-28 22:22 ` [PATCH v2 08/12] revert: add --ff option to allow fast forward when cherry-picking Christian Couder
2010-02-28 22:22 ` [PATCH v2 09/12] cherry-pick: add tests for new --ff option Christian Couder
2010-02-28 22:22 ` [PATCH v2 10/12] Documentation: describe new cherry-pick " Christian Couder
2010-02-28 22:22 ` [PATCH v2 11/12] cherry-pick: add a no-op --no-ff option to future proof scripts Christian Couder
2010-02-28 22:22 ` [PATCH v2 12/12] rebase -i: use new --ff cherry-pick option Christian Couder
2010-03-01 3:49 ` [PATCH v2 00/12] add --ff option to cherry-pick Junio C Hamano
2010-03-01 4:42 ` Daniel Barkalow
2010-03-01 7:00 ` Christian Couder
2010-03-01 8:48 ` Junio C Hamano
2010-03-04 2:06 ` Christian Couder
2010-03-04 3:31 ` Junio C Hamano
2010-03-04 6:55 ` Christian Couder
2010-03-04 20:48 ` Junio C Hamano
2010-03-21 2:01 ` Jonathan Nieder [this message]
2010-03-01 8:20 ` Johannes Sixt
2010-03-01 12:34 ` Paolo Bonzini
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=20100321020120.GA30915@progeny.tock \
--to=jrnieder@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=barkalow@iabervon.org \
--cc=bebarino@gmail.com \
--cc=bonzini@gnu.org \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=s-beyer@gmx.net \
--cc=torvalds@linux-foundation.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).