Re: Fwd: Should "head" also work for "HEAD" on case-insensitive FS?

Jeff King writes: > On Wed, Jul 26, 2017 at 05:49:47PM -0700, Junio C Hamano wrote: > >> What I saw was that a test have ended up with .git/%46%4F%4F when it >> was told to create a ref "FOO" (which indicates that "FOO" was >> passed to the files backend), which later failed to

Re: Fwd: Should "head" also work for "HEAD" on case-insensitive FS?

On Wed, Jul 26, 2017 at 05:49:47PM -0700, Junio C Hamano wrote: > Michael Haggerty writes: > > > I think the most natural thing would be to use different encoding > > rules for pseudo-refs (references like "HEAD" and "FETCH_HEAD") and > > for other references (those

Fwd: Should "head" also work for "HEAD" on case-insensitive FS?

Heh, then I'll forward my response and we are even ;-) -- Forwarded message -- From: Junio C Hamano <gits...@pobox.com> Date: Mon, Jul 10, 2017 at 10:48 AM Subject: Re: Should "head" also work for "HEAD" on case-insensitive FS? To: Michael Hagg

Fwd: Should "head" also work for "HEAD" on case-insensitive FS?

te: Mon, Jul 10, 2017 at 7:52 AM Subject: Re: Should "head" also work for "HEAD" on case-insensitive FS? To: Junio C Hamano <gits...@pobox.com> On Fri, Jul 7, 2017 at 12:34 AM, Junio C Hamano <gits...@pobox.com> wrote: > [...] > The exact detail of the encod

Re: Should "head" also work for "HEAD" on case-insensitive FS?

Junio C Hamano writes: > Once Michael's packed-refs backend stabilizes, we may have a nice > calm period in the refs subsystem and I expect that this will become > a good medium-sized project for a contributor who does not have to > be so experienced (but not a complete

Re: Should "head" also work for "HEAD" on case-insensitive FS?

On Tue, Jul 04, 2017 at 10:19:09AM +0300, Konstantin Khomoutov wrote: > On Tue, Jul 04, 2017 at 12:00:49AM +0200, Ævar Arnfjörð Bjarmason wrote: > > > I don't have a OSX box, but was helping a co-worker over Jabber the > > other day, and he pasted something like: > > > > $ git merge-base

Re: Should "head" also work for "HEAD" on case-insensitive FS?

Jeff King writes: > Ultimately I think the path forward is to have a ref backend that > behaves uniformly (either because it avoids the filesystem, or because > it encodes around the differences). See: > > http://public-inbox.org/git/xmqqvb4udyf9@gitster.mtv.corp.google.com/

Re: Should "head" also work for "HEAD" on case-insensitive FS?

On Tue, Jul 04, 2017 at 10:24:30AM +0200, Ævar Arnfjörð Bjarmason wrote: > I.e. we allow any arbitrary ref sitting in .git/, but presumably we > could just record the original string the user provided so that this > dies on OSX/Windows too: > > $ cp .git/{HEAD,Whatever} > $ git rev-parse

Re: Should "head" also work for "HEAD" on case-insensitive FS?

On Tue, Jul 04 2017, Konstantin Khomoutov jotted: > On Tue, Jul 04, 2017 at 12:00:49AM +0200, Ævar Arnfjörð Bjarmason wrote: > >> I don't have a OSX box, but was helping a co-worker over Jabber the >> other day, and he pasted something like: >> >> $ git merge-base github/master head >> >>

Re: Should "head" also work for "HEAD" on case-insensitive FS?

On Tue, Jul 04, 2017 at 12:00:49AM +0200, Ævar Arnfjörð Bjarmason wrote: > I don't have a OSX box, but was helping a co-worker over Jabber the > other day, and he pasted something like: > > $ git merge-base github/master head > > Which didn't work for me, and I thought he had a local "head"

Should "head" also work for "HEAD" on case-insensitive FS?

I don't have a OSX box, but was helping a co-worker over Jabber the other day, and he pasted something like: $ git merge-base github/master head Which didn't work for me, and I thought he had a local "head" branch until realizing that of course we were just resolving HEAD on the FS. Has