Matthias Gerstner wrote on Mon, Nov 05, 2012 at 10:11:47 +0100:
> On Wed, Oct 31, 2012 at 06:35:23PM +0100, Daniel Shahaf wrote:
> >
> > That's correct but besides the point. The point was that 'svn log' in
> > the trunk/ directory should show ^/A ^/B ^/C if you did the move/copy as
> > I suggest
On Wed, Oct 31, 2012 at 06:35:23PM +0100, Daniel Shahaf wrote:
>
> That's correct but besides the point. The point was that 'svn log' in
> the trunk/ directory should show ^/A ^/B ^/C if you did the move/copy as
> I suggested, but won't if you do it as 'mkdir trunk; cp A trunk;
> cp B trunk; cp C
Matthias Gerstner wrote on Wed, Oct 31, 2012 at 18:25:44 +0100:
> > Did you accomplish that as three individual moves? Try accomplishing
> > it as 'svn cp ^/ ^/trunk' instead.
>
> That didn't change anything. As I see it 'svn move' uses 'svn copy'
> anyway to achieve its results.
>
That's corre
> Did you accomplish that as three individual moves? Try accomplishing
> it as 'svn cp ^/ ^/trunk' instead.
That didn't change anything. As I see it 'svn move' uses 'svn copy'
anyway to achieve its results.
Maybe I chose a too simple example. Actually I have say 50 repositories
each having their
Matthias Gerstner wrote on Wed, Oct 31, 2012 at 10:27:17 +0100:
> > "new" was created in r2 so running 'log' on it will not show earlier
> > revisions. (Well, unless you pass -g) 'log' just walks the history of
> > a node; it won't show revisions in which that node did not exist.
> >
> > But th
On Oct 31, 2012, at 04:27, Matthias Gerstner wrote:
> My use case is that I'm doing a big reorganization if small repositories
> into a large repository. To do this I use 'svnadmin dump/load' and move
> the resulting directories around in the new repository to achieve a new
> structure.
Another
> "new" was created in r2 so running 'log' on it will not show earlier
> revisions. (Well, unless you pass -g) 'log' just walks the history of
> a node; it won't show revisions in which that node did not exist.
>
> But the reference to r1 is not lost; is it present in line 4 of the
> output:
T
Matthias Gerstner wrote on Tue, Oct 30, 2012 at 17:21:39 +0100:
> echo -e "\n here no revision r1 is present\n"
> svn log -v new
"new" was created in r2 so running 'log' on it will not show earlier
revisions. (Well, unless you pass -g) 'log' just walks the history of
a node; it won't show revis
Hello,
I have some trouble wit the logic of the 'svn log' command.
When reorganizing the directory structure in a repository by using 'svn
move' I don't get the desired output from 'svn log' in all
circumstances.
I think this is best demonstrated by this sample script:
-
