I may be mistaken but my understanding is that git-svn cannot be shared with an upstream git repo only a subversion one.
我完全怀念我试图做你所想做的事情,从遥远的宝库拖到颠覆。
我现在做的是用it子做我的SCC,我把档案复制成只控制当地树木的颠覆,然后检查这种颠覆。
我写了一幅地方树苗与当地转树之间的yn。 它只改变了档案,只有我所关心的档案。 然后,我从颠覆性工作树中找到一个正常的<代码>svn ci。
Ok I found the source of my understanding here... http://git-scm.com/docs/git-svn under the heading CAVEATS...
For the sake of simplicity and
interoperating with a less-capable
system (SVN), it is recommended that
all git svn users clone, fetch and
dcommit directly from the SVN server,
and avoid all git
clone/pull/merge/push operations
between git repositories and branches.
The recommended method of exchanging
code between git branches and users is
git format-patch and git am, or just
dcommit’ing to the SVN repository.
Running git merge or git pull is NOT
recommended on a branch you plan to
dcommit from. Subversion does not
represent merges in any reasonable or
useful fashion; so users using
Subversion cannot see any merges
you’ve made. Furthermore, if you merge
or pull from a git branch that is a
mirror of an SVN branch, dcommit may
commit to the wrong branch.
