[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Setting Revision Properties before Commit

From: Mark Phippard <MarkP_at_softlanding.com>
Date: 2005-06-21 14:50:02 CEST

David Weintraub <qazwart@gmail.com> wrote on 06/20/2005 11:43:50 PM:

> > > 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).

There already is an open issue for this:

http://subversion.tigris.org/issues/show_bug.cgi?id=1976

At the time I brought it up on this list, there seemed to be general
agreement that this would be a nice feature to add to svn. There were
concerns expressed about what the UI for this feature should be, so if you
decide to tackle this you should probably post your ideas for the UI
before you start.

I also got the feeling that none of the devs were interested enough in
this feature that they would be tackling it anytime soon. So I think it
will take a patch of some sort being submitted to get this issue jump
started.

> 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).

Whether there are revision properties or not, this always going to be an
issue. The Subclipse and TortoiseSVN projects got together and defined a
standard "spec" that any Subversion client can easily implement to
integrate with issue trackers.

http://svn.collab.net/repos/tortoisesvn/trunk/doc/issuetrackers.txt

Both of these projects implement this spec today, and it offers a fairly
deep GUI integration between Subversion and your issue tracker of choice.
If you decide to enforce the integration with hook scripts, it is also
fairly easy for a CLI user to participate. Here is an example where the
issue tracker is FogBugz, but it could easily be any issue tracker.

http://www.fogcreek.com/FogBugz/docs/40/Articles/SourceControl/TortoiseSVN.html

If this revision property feature were implemented, we would likely
enhavce the spec to also include setting a property. However, until there
is some mechanism for querying revision properties, using log messages
will likely remain the best place for this information.

Mark

_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jun 21 14:50:56 2005

This is an archived mail posted to the Subversion Dev mailing list.