[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

[TSVN] Re: Re: Re: Tag/Branch name checking suggestion.

From: Simon Large <slarge_at_blazepoint.co.uk>
Date: 2005-01-20 16:09:53 CET

Hughes, Bill wrote:
> Simon Large wrote:
>> Which is not so easy. How do you know where the protocol and remote
>> FS ends and the repository begins?
> But there are only a few valid protocols for tsvn to search for aren't
> there?
> Checks for 'file:///' etc starting the URL could be hard coded with
> no risk, at least none that I can see. It's how they're supposed to
> be used isn't it?

What I mean is: for a remote repository, how do you know which bit of
the URL is within the repository and which bit is part of the server
file tree. For example:

http://server.company.com/dir-a/dir-b/bad:name{}/dir-c/dir-d/file

Now can you tell where the top level of the repository is in that URL?
Maybe it's dir-c in which case there is no way that bad:name{} can ever
be checked out to a Windows client. But maybe it is dir-b - then some
clients could check out bad:name{}, but not on Windows.

>> In both cases it would be fairly easy to check for paths
>> ending in CON,
>> AUX, etc. Because almost no-one uses those features anymore,
>> it would be
>> easy to forget that they are still invalid filenames.
> Which virtually guarantees that someone having trouble with it will
> appear on the list :-)

So it might be a good idea to warn them in advance?

Simon

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Thu Jan 20 16:09:50 2005

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.