> > -----Original Message-----
> > From: Phyrefly [mailto:phyrefly.phyre@gmail.com]
> > No, I'm trying to add one new piece of functionality at a
> > time, so we can see where it makes sense to draw the line.
> > Although, having said that, if I can label file B at rev 2,
> > and file A at rev 1, then there's no reason I can't remove
> > the label from file A and label tags/tag_1/A at rev whatever.
> > At this point, the branch holds the label though, not the trunk.
>
> How is this going to work against directory structures? Is everything in a label checked out to a single directory in the working copy, or does it check out the skeleton directory structure with it's root at the highest point that the labelled files fall under, or would we need to provide a root or directory structure in the label itself, or maybe a label would have to be restricted to a single directory?
>
I don't see this as operating any differently from checking out a
single old revision, which automatically leaves out any files (and, I
assume, folders) that didn't exist in that revision. Think of it as a
revision that only applies to some files... Restricting a label to one
folder is definitely not the answer though.
A sample repo. Current rev 10
Root: File_A, Folder_1, Folder_2
Folder_1: File_B, File_C
Folder_2: File_D, File_E, Subfolder_2_1
Subfolder_2_1: File_F
Labels (format File:rev)
Label_1: A:10, B:5, D:7, E:7
Label_2: A:10, D:10, F:10
Checking out Label_1 from root would give you File_A, both folders, no
subfolders, and the three files in their respective folders, at the
correct rev.
Checking out Label_1 from the URL svn://Folder_1 would give you just
file_B in your working copy.
Checking out Label_2 from the URL svn://Folder_1 would give you
nothing. (an empty working copy)
I'm not 100% sure what you were asking, so if this doesn't answer it,
please propose a Label/Checkout that poses that problem. (feel free
to add complexity to the sample repo if necessary)
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 22 00:58:20 2006