post 0.8 development

[Jan Hudec]

On Wed, May 10, 2006 at 08:27:33 -0700, John A Meinel wrote:
> Robert Widhopf-Fenk wrote:
> > It does not matter if it is common in file names, it only
> > must not exist in a branch name and IMHO this restrictions
> > would not harm anyone?
> > 
> > With the same syntax as for -r, e.g.
> > 
> >  bzr diff http://path/to/branch,1..2
> >  bzr diff .,1 http://path/to/branch,2
> >  bzr diff http://path/to/branch,2
> >  ...
> >  
> > Are there any branches around with a "," in the branch
> > (directory) name?  I did not find any public ones.
> > 
> > SVN uses "@", so using it would not cause headache to
> > assimilated svn users.
> > 
> > Robert
> 
> At one point we started using /@, meaning path/to/branch/@1
> I don't remember the official reasons, but we decided to get rid of that
> syntax.
> I'm fine with the comma. I think we should support escaping it, (as in
> http://path/with\,comma/,1..2) But I'm not settled on that.

It's an *URL* -- so http://path/with%2ccomma/,1..2

> I dislike arbitrary "you can't do that" restrictions.

Nobody is making them -- URLs allow anything (when properly escaped, of
course).

> As an old arch hangover, I still create temporary directories with a
> leading comma (helps me realize I can just delete them at anytime in the
> future).
> So I do have paths with commas in them. Albeit rarely, and nothing truly
> important in them.

But not *versioned* paths with them. You don't need to pass names of
unversioned (and unintended for versioning) files to bzr.

-- 
						 Jan 'Bulb' Hudec <bulb at ucw.cz>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : https://lists.ubuntu.com/archives/bazaar/attachments/20060511/c1f37770/attachment.pgp