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

Enhancement for the issue tracker integration

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2007-10-12 22:36:05 CEST

Hi,

As you all know, we have a document on how SVN clients can interact with
issue trackers. This is done with the bugtraq: properties.
(for more info about this:
http://tortoisesvn.net/issuetracker_integration
http://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-bugtracker.html
)

But I recall that during our first discussions about this, some people
asked if we could store the issue ID in a revision property. At that
time, that wasn't really an option because it wasn't possible to do that
in an atomic way - two server round trips were needed (one for the
actual commit, then another for setting the revision property).

Subversion 1.5 has the ability to set revision properties with every
commit (and other commands which create a new revision). I thought we
could use this new feature to add a revision property for those who want
it. Of course, it is also possible to get that revision property when
fetching the log information with SVN 1.5, so it will still be possible
to show the associated bug ID with every log message.

I've already written a proposal on how this could be done:
http://issues.tortoisesvn.net/index.php?do=details&task_id=405

Please comment on this now so we can get the specs right and can
implement them before SVN 1.5 gets released.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Fri Oct 12 22:36:18 2007

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.