You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Greg Hudson <gh...@MIT.EDU> on 2004/10/08 04:01:32 UTC
Re: Which commands are supposed to use the new peg version at
BASE?
On Wed, 2004-10-06 at 11:16, Peter Hercek wrote:
> Version 1.1 introduces peg version at BASE for cat
> diff, blame, switch, merge, update, proplist, propget
> commands.
> It probably does not make sense for add, co, cleanup,
> ci, delete, export, help, import, info, mkdir, move,
> resolved, revert, status since they do not have any
> BASE to take the pegged revision from or do not
> have revision switch at all.
I think copy might want to use a peg rev if you give it a revision
switch (HEAD if the source is a URL, BASE if the source is a wc path).
Likewise for export.
> I'm not sure how it is with propdel, propedit and propset.
No issue there.
> Log command stays as it was (ie the path is searched
> in a revision specified by -r argument instead of being
> pegged to BASE). I'm not sure whether it was intended.
> Is this intentional?
I think that's an oversight or a mistake.
> BTW, svn help move reports that move command can
> use -r argument, but it looks like it is not applicable.
How odd. Also looks like a bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: Which commands are supposed to use the new peg version atBASE?
Posted by Peter Hercek <pe...@syncad.com>.
Hi Greg,
Hmm, I thought I have not had access to this group since
my post here did not appear for about an hour after it was
sent. So I tried my luck once again in the user gropu and Ben
responded.
Here is some more data about the log problem (may be there
is also a small diff problem ... or I do not understand it):
http://www.contactor.se/~dast/svnusers/archive-2004-10/0423.shtml
Let me know if I should fill some issue for the log problem
or the documentation problem.
Thanks,
Peter.
----- Original Message -----
From: "Greg Hudson" <gh...@MIT.EDU>
Newsgroups: gmane.comp.version-control.subversion.devel
Cc: <de...@subversion.tigris.org>
Sent: Friday, October 08, 2004 00:01
Subject: Re: Which commands are supposed to use the new peg version atBASE?
> On Wed, 2004-10-06 at 11:16, Peter Hercek wrote:
> > Version 1.1 introduces peg version at BASE for cat
> > diff, blame, switch, merge, update, proplist, propget
> > commands.
>
> > It probably does not make sense for add, co, cleanup,
> > ci, delete, export, help, import, info, mkdir, move,
> > resolved, revert, status since they do not have any
> > BASE to take the pegged revision from or do not
> > have revision switch at all.
>
> I think copy might want to use a peg rev if you give it a revision
> switch (HEAD if the source is a URL, BASE if the source is a wc path).
> Likewise for export.
>
> > I'm not sure how it is with propdel, propedit and propset.
>
> No issue there.
>
> > Log command stays as it was (ie the path is searched
> > in a revision specified by -r argument instead of being
> > pegged to BASE). I'm not sure whether it was intended.
> > Is this intentional?
>
> I think that's an oversight or a mistake.
>
> > BTW, svn help move reports that move command can
> > use -r argument, but it looks like it is not applicable.
>
> How odd. Also looks like a bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org