Les Mikesell wrote:
> On Wed, 2006-11-29 at 05:30, Gerco Ballintijn wrote:
>
>> The other problem with revision properties, as indicated by Tim Hill,
>> is that they cannot be set at revision creation time. Solving this
>> problem would make them significantly easier to use, and thus more
>> useful.
>
> Is it possible to set them on only the revisions that exist
> in your workspace as you commit? As I've mentioned a few
> times before, it is a common problem that you want to
> tag an exact match to your workspace, including changes
> you've committed, but _not_ include revisions committed
> to the repository by others that you haven't updated to
> in your working copy. CVS lets you do this and it is
> often necessary for concurrent development work. Subversion
> mentions the situation in the manual but provides no way
> to deal with it in the repository. You can copy the workspace
> to a tag which won't match any revision state of the trunk
> or branches, but you are on your own to commit separately
> to wherever else the ongoing work belongs - and then there
> is nothing to associate those commits with the separate
> tag copy. If a different mechanism is going to be added,
> it should be something that can handle these needed
> mixed-revision states.
>
My view is that setting one or more revision properties *during
a commit* is not a different mechanism, merely an unfortunate
oversight in the current implementation of the standard client.
A solution simplies combines the separate actions of commiting
(remembering the new revision number) and setting the properties.
This additional functionality is not a different "tagging"
mechanism.
Different tagging mechanisms are a wholly different discussion.
With regards,
Gerco.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Nov 29 16:53:27 2006