Re: [PATCH] Also handle CVS branches with a '/' in their name

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: [PATCH] Also handle CVS branches with a '/' in their name

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:42:04

Johannes Schindelin [off-list ref] writes:
I track a CVS project which has a branch with a '/' in the branch name.
Since git wants the branch name to be a file name at the same time,
translate that character to a '-'. This should work well, despite the
fact that a division and a difference are completely different :-)
My feeling is that there should be nothing to prevent you from
having a non-flat namespace in .git/refs/heads; i.e. we should
allow ".git/refs/heads/foo/bar".  Some of the existing tools may
be forgetting to call either "mkdir -p $(dirname $ref)" if they
are written in shell, or safe_create_leading_directories(ref) in
C, but I consider that is a bug.

Re: [PATCH] Also handle CVS branches with a '/' in their name

From: Johannes Schindelin <hidden>
Date: 2016-06-15 22:42:04

Hi,

On Wed, 17 Aug 2005, Junio C Hamano wrote:
Johannes Schindelin [off-list ref] writes:
quoted
I track a CVS project which has a branch with a '/' in the branch name.
Since git wants the branch name to be a file name at the same time,
translate that character to a '-'. This should work well, despite the
fact that a division and a difference are completely different :-)
My feeling is that there should be nothing to prevent you from
having a non-flat namespace in .git/refs/heads; i.e. we should
allow ".git/refs/heads/foo/bar".
That may be true, but CVS branches being named "Hänsel/Gretel" do not 
logically denote hierarchies. I never ever saw hierarchical CVS branch 
names with a "/" separator. I saw some with a "." separator.

My feeling is that it would be wrong to map CVS branch names to a 
hierarchy.

Ciao,
Dscho
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help