On Sat, 2012-08-18 at 13:33 -0700, Junio C Hamano wrote:
> Richard Purdie <richard.pur...@linuxfoundation.org> writes:
> > I'd add that I think the commit made for the original problem[1] has
> > fixed this scenario since it now will prefer foo over foo.git also in
> > the fetch case even if the / is removed from the url.
> OK.
> As understand it, these "check various possibilities e.g. $name,
> $name.git $name/.git" were never meant to be a way to encourage
> users to have multiple repositories next to each other under
> confusing names in the first place.  It was merely to allow users to
> have one of them (some may prefer $name/ that is with working tree,
> so we allow $name/.git to be discovered, while some may want to have
> a bare repository at $name.git that is bare, so we also allow it to
> be discovered).  The recent tweak was to favor the case where the
> name asked explicitly by the user is matched first, and it does not
> fundamentally change the intent of the basic design in any way.
> Thanks for confirming that the tweak works well for you.

I'm responsible for "generic" source fetching infrastructure and
unfortunately I haven't been able to prevent users ending up with
"repositories next to each other under confusing names" much as I might
like to. Users tend to manage to find all the corner cases in something
like this :)

> > My test machines
> > don't have that version yet though and I'm left with a problem where git
> > is older than 
> So what do you want to see happen next?

I was a bit confused earlier whether there was any remaining issue. With
the recent versions I've now confirmed there isn't and the bug is fixed
(which I really appreciate). Sorry for the noise.

My remaining question was whether there was any better way to work
around this in older versions of git. I've ended up implementing the
symlink solution I mentioned which whilst ugly, will hopefully put this
issue to rest for me.

 in case anyone cares)



To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to