git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Post 1.7.10 cycle
Date: Tue, 10 Apr 2012 20:55:58 +0200	[thread overview]
Message-ID: <4F84823E.6030308@lsrfire.ath.cx> (raw)
In-Reply-To: <7v1unwtp02.fsf@alter.siamese.dyndns.org>

Am 10.04.2012 02:22, schrieb Junio C Hamano:
> It's now time to pick among the topics that have been cooking in 'next'
> and 'pu' which ones to start moving to 'master' in what order.
> 
> I've already kicked one topic out of 'next' as it regresses the http proxy
> support, but I haven't spent enough time to look at the other topics again
> closely enough to decide.  I was hoping that we could feed a handful of
> topics every few days to 'master'.
> 
> I think the following topics (in 'next') are more or less ready:

> rs/unpack-trees-leakfix

Please apply the following patch before this one.  It makes sure that it
is a pure leak fix.  Without the added check, it'd change the behaviour
slightly: with o->merge == 0, we'd call mark_ce_used() on src[0]; before
it would point to the leaked version, but after the patch it points to
the version that has been added using do_add_entry().  Not sure if this
can lead to any user-visible consequences, but this is cleaner.

-- >8 --
Subject: unpack-trees: don't perform any index operation if we're not merging

src[0] points to the index entry in the merge case and to the first
tree to unpack in the non-merge case.  We only want to mark the index
entry, so check first if we're merging.

Signed-off-by: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
---
 unpack-trees.c |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/unpack-trees.c b/unpack-trees.c
index 7c9ecf6..60b728e 100644
--- a/unpack-trees.c
+++ b/unpack-trees.c
@@ -772,7 +772,7 @@ static int unpack_callback(int n, unsigned long mask, unsigned long dirmask, str
 	if (unpack_nondirectories(n, mask, dirmask, src, names, info) < 0)
 		return -1;
 
-	if (src[0]) {
+	if (o->merge && src[0]) {
 		if (ce_stage(src[0]))
 			mark_ce_used_same_name(src[0], o);
 		else
-- 
1.7.10

      reply	other threads:[~2012-04-10 18:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-10  0:22 Post 1.7.10 cycle Junio C Hamano
2012-04-10 18:55 ` René Scharfe [this message]

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=4F84823E.6030308@lsrfire.ath.cx \
    --to=rene.scharfe@lsrfire.ath.cx \
    --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 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).