[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: Markus Fuchs <svn_at_yeahware.com>
Date: 2006-01-04 00:41:46 CET

> 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 fear I cannot prevent users from managing their repositories by using
svnadmin. As the application I'm talking about is a SCM system with SVN
integration I'm looking for a way to identify changesets modified by any SVN
tool with all their options.
However, you're right that the identification information - if there is
any - has to be exposed through the API (python bindings, in my case).


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Jan 4 00:46:51 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.