Yes I can see what you mean, but it still remains that the proposed 3 part
UID would break if the folder was renamed as the branch id would change.
I would like to see an UUID created when a file/folder is first submitted.
Using the UUID alone would identify the top of the pile version of the item
or you could point to any version using the proposed solution.
/Niels
-----Original Message-----
From: kfogel@newton.ch.collab.net [mailto:kfogel@newton.ch.collab.net] On
Behalf Of kfogel@collab.net
Sent: 15 May 2005 23:30
To: Niels Andersen
Cc: users@subversion.tigris.org
Subject: Re: Enhancement request: Unique file or directory id
"Niels Andersen" <nan@it.dk> writes:
> I work for an organisation which likes to rename projects and products
> all the time especially in mid life. Its also very common that a
> subproject is moved to another major version.
>
> I like to keep documentation like requirements, design and test
> documents in the repository alongside the source code and copies of
released build's.
>
> So if I publish a link to a requirements document, this gets signed
> off but the implementation of the project then gets postponed to a
> later release, I break the link to the old document if I rename the path
to the new name.
>
> I would like a unique number to be attached to any file or directory
> in the repository so that I can reference the item either using the
> current way or using the shorthand with the UID.
>
> When an item is branched/copied the new branch/copy should get a new
number.
> When renamed the the number should be retained.
I think this is probably part of true atomic rename support,
http://subversion.tigris.org/issues/show_bug.cgi?id=898. See also
http://subversion.tigris.org/issues/show_bug.cgi?id=1525.
Best,
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon May 16 02:47:27 2005