On Tue, Jun 19, 2012 at 12:37:06PM +0200, Vincent Lefevre wrote:
> Well, not all copy events should be affected. For instance, if a file
> is moved from a directory to another one, this should be shown in the
> log. Here what is copied is not the file itself, but the directory
> above it.
True. An
On 2012-06-19 11:53:37 +0200, Stefan Sperling wrote:
> On Tue, Jun 19, 2012 at 09:46:20AM +0200, Vincent Lefevre wrote:
> > On 2012-06-19 01:29:18 -0400, Greg Stein wrote:
> > > In 1.6, we erroneously used the containing directory's revision for the
> > > file in certain cases. 1.7 is correct: the
On Tue, Jun 19, 2012 at 09:46:20AM +0200, Vincent Lefevre wrote:
> On 2012-06-19 01:29:18 -0400, Greg Stein wrote:
> > In 1.6, we erroneously used the containing directory's revision for the
> > file in certain cases. 1.7 is correct: the file is not changed until r4.
> > Maybe the directory has, bu
On 2012-06-19 01:29:18 -0400, Greg Stein wrote:
> In 1.6, we erroneously used the containing directory's revision for the
> file in certain cases. 1.7 is correct: the file is not changed until r4.
> Maybe the directory has, but that is independent of the file.
But in this case, is it normal that r
In 1.6, we erroneously used the containing directory's revision for the
file in certain cases. 1.7 is correct: the file is not changed until r4.
Maybe the directory has, but that is independent of the file.
Cheers,
-g
On Jun 19, 2012 3:02 AM, "Vincent Lefevre" wrote:
> I've upgraded Subversion f
I've upgraded Subversion from 1.6.17 to 1.7.5 (Debian/unstable).
And there's the following problem:
Subversion 1.7.5 no longer notices a change of revision of some file
when a parent directory has been moved. In particular, this yields
incorrect keyword expansion.
The bug can be reproduced with t
6 matches
Mail list logo
