From: Junio C Hamano <gitster@pobox•com>
To: Jeff King <peff@peff•net>
Cc: git@vger•kernel.org, Michael Haggerty <mhagger@alum•mit.edu>
Subject: Re: [PATCH] refs: speed up is_refname_available
Date: Thu, 11 Sep 2014 10:07:28 -0700 [thread overview]
Message-ID: <xmqqy4tqdr1r.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <20140910101730.GA12399@peff.net> (Jeff King's message of "Wed, 10 Sep 2014 06:17:31 -0400")
Jeff King <peff@peff•net> writes:
> This has a fairly straightforward conflict with the ref-transaction
> stuff in pu. The "oldrefname" parameter to is_refname_available became a
> list of items;
Hmph, the trouble I had while reading the conflicts was about the
new "we skip these when repacking", not "oldrefname".
Will check your suggested resolution later today. Thanks.
next prev parent reply other threads:[~2014-09-11 17:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 10:17 [PATCH] refs: speed up is_refname_available Jeff King
2014-09-10 11:11 ` [PATCH v2] " Jeff King
2014-09-10 22:21 ` Junio C Hamano
2014-09-11 1:39 ` Jeff King
2014-09-10 22:22 ` Junio C Hamano
2014-09-11 17:07 ` Junio C Hamano [this message]
2014-09-11 18:31 ` [PATCH] " Jeff King
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=xmqqy4tqdr1r.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=mhagger@alum$(echo .)mit.edu \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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