Re: git-svn and repository hierarchy?

On Sat, Feb 28, 2009 at 06:59:22PM +0100, Michael J Gruber wrote:

Josef Wolf venit, vidit, dixit 27.02.2009 23:05:

quoted

On Fri, Feb 27, 2009 at 06:45:44PM +0100, Michael J Gruber wrote:

quoted

Josef Wolf venit, vidit, dixit 27.02.2009 18:12:

quoted

On Wed, Feb 25, 2009 at 10:26:10AM +0100, Michael J Gruber wrote:

quoted

Josef Wolf venit, vidit, dixit 24.02.2009 23:34:

[ ... ]

quoted

quoted

  (cd git-svn-repos; git pull ../clone1)

Gives you 1-2-3-4

quoted

  (cd git-svn-repos; git svn rebase)

Does nothing here (but is good practice)

quoted

  (cd git-svn-repos; git svn dcommit)

Creates 2-3-4 on the svn side. *Then rebases* your master, which creates
1-2'-3'-4' on master. Note that 2 is different from 2' (git-svn id).

So the sha1 is not preserved when it goes through svn?

No. Once your commits come back from svn through git-svn they have an
additional line in the commit. Also, the commit time time will be
different, and the author name might be depending on your name remapping.

But what prevents this new commit from being thrown back to svn again,
and looping over and over again?

For some reason, I keep getting conflicts.  And the most annoying
part is that even if I resolve the conflict in git-svn-repos, it
gets propagated as a (spurious) conflict down to all the clones.
Here's the recipe:

(
  set -ex

  # create test directory
  #
  TESTDIR=`mktemp --tmpdir=. git-svn-hierarchy-test-XXXXXXXX`
  rm -rf $TESTDIR
  mkdir -p $TESTDIR
  cd $TESTDIR

  SUBVERSION_REPOS=file://`pwd`/subversion-repos

  # create subversion repos with some history
  #
  svnadmin create subversion-repos
  svn -m "create standard layout" mkdir \
      $SUBVERSION_REPOS/trunk \
      $SUBVERSION_REPOS/branches \
      $SUBVERSION_REPOS/tags
  svn co $SUBVERSION_REPOS/trunk subversion-wc
  echo change1 >>subversion-wc/test
  svn add subversion-wc/test
  svn ci -m "commit 0" subversion-wc

  # create git-svn-repos
  #
  git svn init --stdlayout $SUBVERSION_REPOS git-svn-repos
  (cd git-svn-repos; git svn fetch)

  # create some clones
  #
  git clone git-svn-repos clone1
  git clone git-svn-repos clone2
  git clone git-svn-repos clone3

  # work on clones, pull work into git-svn-repos when we're done
  #
  for clone in 1 2 3; do
    (
      cd clone$clone
      git pull --rebase
      for commit in 1 2 3; do
        echo change $clone $commit >>test
        git commit -a -m "commit $clone $commit"
      done
    )
    (cd git-svn-repos; git pull --rebase ../clone$clone)
  done

  # commit from svn
  #
  ( cd subversion-wc; echo change s >>test; svn ci -m "commit s")

  # git-svn-rebase gives us a conflict
  #
  ( cd git-svn-repos; git svn rebase )

  # which we immediately resolve
  #
  (
    cd git-svn-repos
    (
      echo change1
      echo change s
      echo change 1 1
    ) >test
    git add test
    git rebase --continue
  )

  (cd git-svn-repos; git svn dcommit)

  # Although we have resolved the conflict, spurious conflicts are
  # propagated to the clones
  #
  for clone in 1 2 3; do
    ( cd clone$clone ; git pull --rebase)
  done
)