Re: Adding changeset-like functionality to subversion

Noel Yap <yap_noel@yahoo.com> writes:
> --- Peter Davis <peter@pdavis.cx> wrote:
> > > I don't think this should make a
> > > big difference so long as one can query what the
> > > previous and next revisions are for any given
> > > revision.
> >
> > Just subtract or add 1 to the revision number. If
> > you are talking about next
> > and previous revisions on a branch, then use
> > something like 'svn status
> > - --strict http://repos/path/to/branch' (IIRC, that
> > might be wrong).

That is incorrect. You can however, use svn log to see which revision
numbers represent changes on your branch. For example:

svn log --strict http://svn.collab.net/repos/svn/branches/fs-convert-2490/

(If you don't use --strict, you get all log messages where files under
that directory have changed, and since a branch is a copy, that means
log msgs of files going back to the dawn of time).
 
> I don't understand. If revisions were repo-global,
> then the next revision on a branch won't be the
> current revision plus one if a commit occurred on
> another branch after the current revision.

That is correct. The next rev on a branch is not necessarily the
current rev + 1, but it could be.

> What am I missing here?

Nothing as far as I can tell. Perhaps the bogus status command above
confused you?

-Fitz

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Oct 8 23:31:16 2002