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

Re: Should all sub-commands accept a peg-revision?

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: 2004-10-23 23:55:40 CEST

Josh Pieper <jjp@pobox.com> writes:

> Currently diff and merge accept a "peg revision", it gives the history
> tracing algorithm a place to start when looking for the actual node
> revisions to operate on. Other sub-commands that perform history
> tracing (cat, ls, propget, ...) don't accept peg revisions, and in
> fact don't currently perform history tracing for URLs, only for
> working copy paths.
> This is an inconsistency in our UI that probably should be resolved.
> I have a patch (attached) to add peg revisions to commands that used
> to trace history but didn't take the peg revision.

In my design for peg and range revisions, I intended for all *all*
subcommands which accepted paths or URLs to recognize the PATH@PEG
syntax -- not just diff and merge. Until this is true, I consider the
feature/fix only partially complete.

To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 23 23:58:16 2004

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

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