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

Re: peg revision / svn_client_merge_peg ?

From: Benjamin Pflugmann <benjamin-svn-dev_at_pflugmann.de>
Date: 2004-09-10 17:52:08 CEST


On Fri 2004-09-10 at 17:33:52 +0200, Martin Hauner wrote:
> 1) what exactly is a peg revision?

If you say, "give me /path/file at revision 43", Subversion goes to
revision 43 and looks for /path/file.

If you say "give me /path/file at revision 43, pegged at revision 50",
Subversion goes to the peg revision, 50, looks for /path/file and then
follows that back to revision 43, regardless of the name it had in
revision 43.

That feature is mainly useful, when a file got renamed/moved/copied in
the past, and in conjuntion with a working copy, where the peg
revision is automatically filled in to be BASE, IIRC. (But it's not
limited to that).

> 2) from an svn client perspective is there any need to support both
> merge methods? Is there another use case to have two source
> paths in svn_client_merge apart from handling renames?

Dunno. Someone else needs to answer this.



To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Sep 10 17:52:36 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.