Hi, thanks for your reply.
I have a few final comments on this matter.
I think that you and SVN have the correct idea, that when you run 'svn log
file:///tmp/test/svn_repo/trunk', then you are asking for the history of the
trunk sub-directory, which didn't exist (in my previous example) more
On Tue, Jun 19, 2007 at 09:21:56AM +0200, David Purdy wrote:
On Mon, May 28, 2007 at 04:43:04PM +0200, David Purdy wrote:
git-svn fetch --follow-parent does not work correctly for cases where a
parent of the directory you're tracking is moved.
Hi David, can you please check with
On Tue, Jun 19, 2007 at 09:21:56AM +0200, David Purdy wrote:
On Mon, May 28, 2007 at 04:43:04PM +0200, David Purdy wrote:
git-svn fetch --follow-parent does not work correctly for cases where a
parent of the directory you're tracking is moved.
Hi David, can you please check with
On Mon, May 28, 2007 at 04:43:04PM +0200, David Purdy wrote:
Package: git-svn
Version: 1:1.4.4.4-2
Severity: normal
git-svn fetch --follow-parent does not work correctly for cases where a
parent of the directory you're tracking is moved.
Hi David, can you please check with git-svn
On Mon, May 28, 2007 at 04:43:04PM +0200, David Purdy wrote:
Package: git-svn
Version: 1:1.4.4.4-2
Severity: normal
git-svn fetch --follow-parent does not work correctly for cases where a
parent of the directory you're tracking is moved.
Hi David, can you please check with git-svn version
Package: git-svn
Version: 1:1.4.4.4-2
Severity: normal
git-svn fetch --follow-parent does not work correctly for cases where a
parent of the directory you're tracking is moved.
eg:
SVN server has these files in r1:
/a/b/c/1.txt
/a/b/c/2.txt
/a/b/c/3.txt
And in r2 /a/b/ was moved to /x:
6 matches
Mail list logo
