Thread (18 messages) flat view 18 messages, 7 authors, 2016-06-15

Re: remote#branch

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

Hi,

On Tue, 16 Oct 2007, Jan Hudec wrote:
If it is a fragment, than "#" is the only correct separator and should 
stay that way.
You did not listen, did you?  '#' is allowed in ref names.  Therefore this 
character really would lock us in to only ever reference _one_ and _only_ 
one remote branch at a time.  This might have worked for cogito, but it 
does not for git.

So, I say it again, '#' is _out_.
If it is not a true fragment, than we might want to phase it out in 
favor of something else. But I would strongly prefer staying within 
characters allowed in URI (as per rfc2396).
If you do that, "http://<xyz-with-branch>" would be ambiguous, wouldn't 
it?  This would already reference an HTTP resource, and you could not 
embed refnames into the URL.
As for multiple branches, separating them with "," feels logical to me, 
no matter what separates them from the repository path. On the other 
hand given that neither ":" nor "@" is allowed in refnames, reusing the 
same separator would make sense especially if git switched to either of 
those.
',' is allowed in ref names, so ',' is out.

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