From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jeff King <peff@peff.net>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
GIT Mailing-list <git@vger.kernel.org>,
"Hart, Darren" <darren.hart@intel.com>,
"Ashfield, Bruce" <Bruce.Ashfield@windriver.com>
Subject: Re: Alternates corruption issue
Date: Fri, 03 Feb 2012 14:40:19 +0000 [thread overview]
Message-ID: <1328280019.3895.112.camel@ted> (raw)
In-Reply-To: <20120202215913.GA26727@sigill.intra.peff.net>
On Thu, 2012-02-02 at 16:59 -0500, Jeff King wrote:
> On Tue, Jan 31, 2012 at 04:22:58PM -0600, Jonathan Nieder wrote:
>
> > Anyway, thanks for explaining. Hopefully I can get to this soon and
> > factor out a common function for get_repo_path and enter_repo to call
> > so playing with the ordering becomes a little less scary. ;-)
>
> So here's what I think we should apply to fix the particular issue that
> Richard mentioned at the start of this thread.
>
> Besides tweaking the ordering, the main contribution is a set of tests
> that actually check some of these ambiguous cases (especially checking
> the fact that both code paths behave identically!). I didn't factor the
> logic into a common function, but doing so should be a little safer on
> top of these tests, if you're still interested.
I didn't have much to add to the discussion yesterday but this solution
looks good to me and should resolve the problems I was seeing.
Thanks!
Richard
prev parent reply other threads:[~2012-02-03 14:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 14:05 Alternates corruption issue Richard Purdie
2012-01-31 19:39 ` Jeff King
2012-01-31 20:25 ` Junio C Hamano
2012-01-31 20:44 ` Jeff King
2012-01-31 21:40 ` Jonathan Nieder
2012-01-31 21:47 ` Jeff King
2012-01-31 21:55 ` Jonathan Nieder
2012-01-31 22:05 ` Jeff King
2012-01-31 22:22 ` Jonathan Nieder
2012-01-31 22:42 ` Jeff King
2012-01-31 22:59 ` Jonathan Nieder
2012-02-02 21:59 ` Jeff King
2012-02-03 0:47 ` Junio C Hamano
2012-02-03 12:02 ` Jeff King
2012-02-03 17:38 ` Junio C Hamano
2012-02-03 21:29 ` Jeff King
2012-02-03 21:51 ` Junio C Hamano
2012-02-03 21:53 ` Jeff King
2012-02-03 14:40 ` Richard Purdie [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=1328280019.3895.112.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=Bruce.Ashfield@windriver.com \
--cc=darren.hart@intel.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
--cc=peff@peff.net \
/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).