On Nov 26, 2010, at 01:58, Ewgenij Sokolovski wrote:
>> I believe he's thinking of "svnput" whose source is here:
>>
>> http://svn.apache.org/repos/asf/subversion/trunk/tools/examples/svnput.c
>>
>> Or you could probably write something equivalent using any of the language
>> bindings.
>
> I lo
Hello,
I would appreciate advice for how to find out the rev number where a file was
deleted or moved.
I expected this command:
svn log -v -r 1:head "file:///[...]/xx/a...@1"
to show all revs including the deleting rev (as last shown rev),
but that doesn't work. The command fails.
Does anybo
Hello!
I'm used to "svn cp" within the same WC, everything seems to work fine.
I just read this warning and now I wonder if this is relevant for my use case.
svn help cp
[...]
WARNING: For compatibility with previous versions of Subversion,
copies performed using two working copy paths (WC -> WC)
> From: svn-u...@web.de [mailto:svn-u...@web.de]
>
> I would appreciate advice for how to find out the rev number where a file
> was deleted or moved.
>
> I expected this command:
> svn log -v -r 1:head "file:///[...]/xx/a...@1"
Yeah. This is annoying. Once a file is deleted, I can't svn log i
On Nov 26, 2010, at 22:33, Edward Ned Harvey wrote:
> Yeah. This is annoying. Once a file is deleted, I can't svn log it
> anymore. Even if I specify a rev where the file existed.
Certainly not if you use an operative revision. You would need to use a peg
revision for that. The book explains
I think the problem is: if a file inherits mergeinfo from somewhere
above the wc root, then that mergeinfo won't be preserved in the copy
target.
In other words, svn will recurse to find a parent/ancestor from which
mergeinfo is inherited only up to the wc root, but won't connect to the
repository
