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

Re: Identifying changesets

From: William Nagel <bill_at_stagelogic.com>
Date: 2006-01-04 20:15:25 CET

On Jan 3, 2006, at 6:41 PM, Markus Fuchs wrote:

>> Dump/filter/load doesn't renumber revisions by default. It only
>> renumbers if you use --renumber-revs, so with proper policies for
>> filtering your repository to remove data you should be safe using
>> revision numbers as a static identifier. As to some low-level id
>> other than revision numbers, I am not aware of any. If they exist, I
>> doubt they are exposed through the API, and if they're not exposed
>> then they're not necessarily going to be safe across SVN version
>> upgrades (especially major revision upgrades that involve schema
>> changes).
> What exactly do you mean by "proper policies"?

I mean organizational policies. For instance, a policy that states
"thou shalt not use --renumber-revs when dumping/loading the
repository". If desired, that policy could then be enforced by only
exposing a wrapper around svndumpfilter that would not accept --

> I fear I cannot prevent users from managing their repositories by
> using
> svnadmin. As the application I'm talking about is a SCM system with
> integration I'm looking for a way to identify changesets modified
> by any SVN
> tool with all their options.

Aha, I understand. You're developing a system that integrates with
SVN in the general case, not internal tools that will be integrating
only with a specific organization's repositories/development

In that case, you're probably out of luck as far as a built-in safe
way to get the information you want. I'd probably consider using
properties that are proprietary to your system to maintain that
data. That way you can define properties that your system will set/
read and document that they should only be touched by the automated
systems. If you wanted, you could even go so far as to provide
prebuilt hook scripts that the users could use to enforce that those
properties would only be set by your system.

> However, you're right that the identification information - if
> there is
> any - has to be exposed through the API (python bindings, in my case).

As far as I know revision numbers are the only exposed unique
identifier for revisions.


> Thanks,
> Markus
> ---------------------------------------------------------------------
> 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 Jan 4 20:51:55 2006

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

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