Re: [PATCH 1/3] retain reflogs for deleted refs

Alexey Muranov [off-list ref] writes:

On 26 Jul 2012, at 14:47, Nguyen Thai Ngoc Duy wrote:

quoted

So we haven't found any way to present both branches "foo" and
"foo/bar" on file system at the same time. How about when we a new
branch introduces such a conflict, we push the new branch directly to
packed-refs? If we need either of them on a separate file, for fast
update for example, then we unpack just one and repack all refs that
conflict with it. Attempting to update two conflict branches in
parallel may impact performance, but I don't think that happens often.
-- 
Duy

How about simply deprecating "/" in branch name?

Err, it's not like nobody's using this feature (Junio does a heavy use
of it in particular) ...

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

On Thu, Jul 26, 2012 at 06:41:09PM +0200, Matthieu Moy wrote:

quoted

How about simply deprecating "/" in branch name?

Err, it's not like nobody's using this feature (Junio does a heavy use
of it in particular) ...

Not to mention git itself, as it splits up the refs/remotes hierarchy
into subdirectories. I think deprecating "/" is out of the question.

-Peff

On 26 Jul 2012, at 18:59, Jeff King wrote:

Not to mention git itself, as it splits up the refs/remotes hierarchy
into subdirectories. I think deprecating "/" is out of the question.

-Peff

Ok, i guess you know better than me, my vision of Git is probably still too simplistic.

-Alexey.