Vincent Lefevre wrote:
Couldn't peg-rev be also taken into account to translate a working copy
object into a URL? This would make sense if the parent directory has
been renamed: as peg-rev is used to point to some object in the past,
one should consider what the URL was in the past.
No,
Vincent Lefevre wrote:
On 2010-03-30 09:31:27 -0400, C. Michael Pilato wrote:
Nobody should be trying to run 'svn cat some/fil...@50' if what they mean is
follow the history of some/file.c back to r50 and cat the contents there.
That's just not the correct syntax for invoking the algorithm,
On 2010-03-30 12:12:59 -0400, C. Michael Pilato wrote:
Interactions in the working copy with the path some/file.c only make sense
if there is actually such a path in the working copy. If some/file.c is
deleted in r51, then either it isn't in your working copy (because you've
updated past r50)
Vincent Lefevre wrote:
On 2010-03-30 12:12:59 -0400, C. Michael Pilato wrote:
Interactions in the working copy with the path some/file.c only make sense
if there is actually such a path in the working copy. If some/file.c is
deleted in r51, then either it isn't in your working copy (because
On Tue, Mar 30, 2010 at 03:21:45PM -0400, C. Michael Pilato wrote:
Vincent Lefevre wrote:
On 2010-03-30 12:12:59 -0400, C. Michael Pilato wrote:
Interactions in the working copy with the path some/file.c only make sense
if there is actually such a path in the working copy. If some/file.c
On 2010-03-30 21:36:27 +0200, Stefan Sperling wrote:
Maybe we could some day extend peg revision syntax so that every
component of a path can be pegged?
So what Vincent wants would be something like this:
$ svn cat @50/some/file.c
I almost proposed this, but the syntax would not be
C. Michael Pilato wrote:
Vincent Lefevre wrote:
Hi,
The description of the Peg Revision Algorithm on
http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.advanced.pegrevs
is incomplete. It doesn't say how item is identified when it is
relative to a working copy. This is
Greg Hudson wrote:
On Mon, 2010-03-29 at 12:07 -0400, Julian Foad wrote:
Some possible interpretations are
* Find the repository URL of './some/deep/file.c', and [...]
I'll mention a related interpretation, which is to use the repository
URL of the parent directory and append file.c to
On Mon, 2010-03-29 at 12:07 -0400, Julian Foad wrote:
Some possible interpretations are
* Find the repository URL of './some/deep/file.c', and [...]
I'll mention a related interpretation, which is to use the repository
URL of the parent directory and append file.c to it.
This is a little
Hi,
The description of the Peg Revision Algorithm on
http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.advanced.pegrevs
is incomplete. It doesn't say how item is identified when it is
relative to a working copy. This is particularly important when
the directory in question has been
10 matches
Mail list logo
