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

Re: Screwed Revision Numbers in SVN

From: Andy Levy <andy.levy_at_gmail.com>
Date: Tue, 27 Jan 2009 22:07:25 -0500

On Tue, Jan 27, 2009 at 20:17, Rez <pons32_at_hotmail.com> wrote:
> I just did a test migration from cvs to svn and downloaded both RapidSVN and
> SmartSVN Windows clients, checked out some modules or projects and in the
> right pane I see the file and folder revision numbers not adhering to most
> version control conventional format, as in, 1.1, 1.2, 1.3 but in SVN format
> and how SVN bumps up the entire repository revision every time an iota of
> data is changed.
> So nuaturally my migration imported about 15000 revisions. Is there anyway
> to tell the client applications to show the real file revision in their
> sequential format as practiced by CVS, ClearCase, Perforce and many other
> conventional version controls?

What you're seeing is a fundamental difference in the versioning
philosophy between SVN and those other systems. See

A version number other than the revision number would be a special
property or meaning that you've attached to that file, so you would
need a custom client to pick that up and display it. And set it each
time you commit a change to each file. It gets unwieldy fast because
SVN just plain isn't meant to work that way.

> It's so much easier to discuss file
> revisions in conventional format such as what changed in rev 1.3 of
> hello.java vs. its 1.2 revision, one automatically would know that we're
> discussing the next revision of the file as opposed to SVN's format
> comparing hello.java 11252(being 1.1) vs. 13605(heing 1.2), how would one
> discern that 13605 is only revision 1.2 of the file?

By looking at the file's log history.


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-01-28 04:08:19 CET

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.