> > David Weintraub wrote:
> > > However, the "svn propset" command doesn't allow me to set the value
> > > of a revision property until the revision itself has been committed.
> > > Is this an oversight? Is it considered a bug, or is there a reason
> > > why
On 20 Jun 2005 15:56:20 -0500, kfogel@collab.net <kfogel@collab.net> wrote:
> No, these are unversioned revision properties, so they have no
> counterpart on the working copy side, so it is okay to set them. It
> is an oversight that we don't offer a convenient way to change them on
> the txn before it is promoted to a revision; however, you could do it
> via a program written using the bindings.
So, this was an oversight then? Can I submit a bug against this? Right
now, for submitting a bug number, each Subversion client GUI does
different things to circumvent this particular issue which means that
each user could be doing this a different way (if at all).
If there was a standard way to set a subversion revision property, all
of the different Subversion client GUIs would use the same method (and
I could enforce it with a hook).
I use to work as a ClearCase admin, and ClearCase had something
similar to hooks called "triggers". The problem is that ClearCase
trigger scripts executed on the client. This gave me a bit more power
(I could interact with the client), but it meant making sure each
client installation was just so. With Subversion, I don't care which
client the developer prefers since the hook scripts run on the server.
Writing my own bindings puts me in the predicament of wondering about
the configuration of the client systems.
--
David Weintraub
qazwart@gmail.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 21 05:44:30 2005