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

Re: missing db/revs, db/revprops and db/current files?

From: Ryan Schmidt <subversion-2008c_at_ryandesign.com>
Date: Sat, 20 Sep 2008 15:01:00 -0500

On Sep 20, 2008, at 3:59 AM, Daniel Shahaf wrote:

> Ryan, I think you are confusing two different meanings of the term
> 'revision'.

Wow. I think you're right, and I'm not. I don't like it when I'm not
right... :-)

> In skip-deltas, the term 'revision' means:
>
> For the purposes of this document, we will pretend that
> revisions of a
> file are numbered starting from 0. In reality, this number
> corresponds to the "change count" field of a node-revision in each
> filesystem back end.

I guess I never read that bit, or never got out of it what it was
trying to tell me.

> In the Subversion UI and API, the term 'revision' means[1]:
>
> The number of commits to a repository.
>
>
> I'm not an FS expert, but as far as I know these two meanings are
> entirely unrelated.
>
> Daniel
>
> [1] Not entirely accurate, but close enough for the purpose of this
> discussion.

Yeah. Well this is entirely confusing.

It's been hammered into me so many times that a revision is of the
repository as a whole. Files don't have revisions; the repository does.

Could the skip-deltas document perhaps be persuaded not to use the
term "revision" when it isn't used the way the term "revision" is
used everywhere else in the Subversion universe? :-)

I guess what this means is that you can't know at all what impact a
missing rev file will have on the repository based on its number.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-20 22:01:25 CEST

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