On Mon, Jul 27, 2020 at 1:21 AM Tommaso Ercole <Tommaso.Ercole@xxxxxxxx> wrote: > > Hi all and thanks for the answers. > > By my understanding it seems that you are aware of all the problems and you have just in place a solution for the future. > > I will just wait for it. > > Thank you really much for your effort, best regards, > Tommaso Ercole > > P.S. btw this chat is it private between us or published somewhere, I just thought about it now, when I saw my phone number on my signature... It's a public list, which anyone can register for, and it also has multiple archives, like: https://lore.kernel.org/git/DM5PR1801MB20762477763E6298C7FE6315F0770@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx/ I don't think there's any way to scrub the data now. Even if it was removed from lore.kernel.org as a one-off, the original email was delivered to the entire list. > > > -----Original Message----- > From: Junio C Hamano <gitster@xxxxxxxxx> > Sent: venerdì 24 luglio 2020 22:44 > To: Jeff King <peff@xxxxxxxx> > Cc: Taylor Blau <me@xxxxxxxxxxxx>; Tommaso Ercole <Tommaso.Ercole@xxxxxxxx>; git@xxxxxxxxxxxxxxx > Subject: Re: Creation of a branch named that has a directory prefix equal to the name of another branch fail. > > Jeff King <peff@xxxxxxxx> writes: > > > Note that even though packed-refs does not have this limitation, we > > still enforce it in order to avoid headaches when moving between loose > > and packed refs. > > > > Likewise, we'll probably[1] continue to enforce it with reftables, at > > least for a while, to make things less confusing when pushing and > > pulling between repositories with different storage. > > Yup, that coincides with my understanding. > > The files backend could also learn encoding/decoding refnames and that could be used to transition, if/when we decide to discard the "refs are organized in a directory-tree like fashion" design we have been using, to a new world order where a branch M and branches M/A, M/B, and M/C can co-exist. Encoding/decoding refname to map to the filename would also help those on case insensitive filesystems. > > Thanks to the recent preparation work for reftable, we are ensuring that we do not leave direct accesses to $GIT_DIR/refs/* in our codebase outside the files backend implementation, such a transition hopefully is getting much easier to do than before.
