Hi,
I guess that your command "find ..." will also change the pristine
copies localized in a subdirectory of the .svn directory.
On 15/02/2011 04:23, Ed wrote:
Hi,
Can someone check if this is a bug?
Script to reproduce:
~/test$ svnadmin create bar
~/test$ mkdir foo
~/test$ cd foo
~/test/f
And you forgot to do svn update after the svn commit.
On Feb 14, 2011, at 9:57 PM, Andy Levy wrote:
> Make sure that your find/sed combo is excluding .svn directories (for
> some reason, I'm not able to run it on OS X). If you modify both the
> "visible" file in the working copy AND the pristine copy of it,
> Subversion won't detect the change.
FWIW
On 2/14/2011 7:23 PM, Ed wrote:
Hi,
Can someone check if this is a bug?
Script to reproduce:
~/test$ svnadmin create bar
~/test$ mkdir foo
~/test$ cd foo
~/test/foo$ svn co file:path/to/bar
~/test/foo/bar$ echo "testing this file" > A.txt
~/test/foo/bar$ svn add A.txt
~/test/foo/bar$ svn c
On Mon, Feb 14, 2011 at 22:23, Ed wrote:
> Hi,
>
> Can someone check if this is a bug?
>
> Script to reproduce:
>
> ~/test$ svnadmin create bar
> ~/test$ mkdir foo
> ~/test$ cd foo
> ~/test/foo$ svn co file:path/to/bar
> ~/test/foo/bar$ echo "testing this file" > A.txt
> ~/test/foo/bar$ svn ad
Hi,
Can someone check if this is a bug?
Script to reproduce:
~/test$ svnadmin create bar
~/test$ mkdir foo
~/test$ cd foo
~/test/foo$ svn co file:path/to/bar
~/test/foo/bar$ echo "testing this file" > A.txt
~/test/foo/bar$ svn add A.txt
~/test/foo/bar$ svn ci A.txt -m "test"
~/test/foo/bar$
