Adding to Ryan's suggestion,
You could make trunk to contain the overlapping files. This is assuming
that they are identical.
If they are not then the cutomer's branch will contain the copy
associated with their release.
Thanks
Lakshman
-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2006Q1@ryandesign.com]
Sent: Tuesday, 28 March 2006 11:05 PM
To: James Courtier-Dutton
Cc: users@subversion.tigris.org
Subject: Re: Labels
On Mar 28, 2006, at 13:38, James Courtier-Dutton wrote:
> I want to be able to label each file with a tag that indicates the
> purpose of the file.
>
> For example, I might have one set of files for one customer, and
> another set of files for another customer, with some overlap between
> the files.
>
> I would then want to be able to filter the view of the files in the
> repository based on these labels. I would than want to tag the set
> based on the view.
> So, later I could see which versions of which files were sent to
> customer A on date xyz.
>
> I can currently do tagging, but I cannot seem to apply any label and
> tag based on the label. I can only currently do tagging to a file or
> an entire directory.
>
> Also, if I tag a file for one customer, and that same file has to go
> to a second customer, the tagging increases the revision number, so it
> looks like a different file.
> So, is there any way to tag a file in the repository with two
> different tags, and not have the revision number different?
You are assigning meaning to the revision number which is not
implied. It is merely "the number of changes that have occurred in
the repository." Nothing more. Revisions apply to the repository as a
whole, not individual files. Thus, a file in the repository at
revision X is not necessarily different from the file in the
repository at revision X + N.
Subversion does not have labels. You can invent them, by using things
like "svn propset mylabel foo" but there is no facility by which you
could then search for all files having property "mylabel" set to
"foo", so this is probably not much use to you.
I don't think Subversion currently can accomodate what you're asking
for, at least, not in the way you're asking for it.
It sounds like a Subversion way to do what you want might be to have
a separate branch for each customer and to merge relevant changesets
between them. Branching is described in the free Subversion book at
http://svnbook.org .
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Mar 29 06:44:50 2006