On Mon, Dec 8, 2008 at 1:26 PM, Grzegorz Kossakowski wrote: > > After doing that git svn rebase resulted in: > [really long list of revisions] > r707379 = f61a2d30b6ac5a5136b46fa2b9b5b91e4763feb1 > r710118 = 40997fe552e8581b75b08fed41a6b63a33d58bdf > r720135 = a8160766ec40fd7ebf95bfa7cebfa50dfa2f9c3a > r720180 = b094a222bab3671c8277087e7a96589ec76dd5e4 > r720182 = 736b8ed6519c64ad120de2ccf08f135062ee09db > Done rebuilding .git/svn/origin/trunk/.rev_map.13f79535-47bb-0310-9956-ffa450edef68 > Current branch master is up to date. > > Is this expected output? Yes. The rfoo = sha1hash part is git-svn rebuilding its index. "Current branch master is up to date" is git-svn calling "git rebase <svn-branch>", and git saying that there is nothing to do, since there have been no svn commits to that branch since the last time you ran git svn rebase (or since you cloned the git mirror, or since the last time the git mirror pulled from svn). Peter Harris -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
