Re: [PATCH 2/3] git-svn: documentation updates

> Eric Wong <normalperson@yhbt.net> writes:
> 
> > Both push and pull are git/bk/hg(?)-specific terms; most SVN users are
> > not accustomed to them.  Using 'pull' with git-svn has already been
> > discouraged for a while (since the introduction of dcommit); and
> > having a 'push' without a 'pull' would be very confusing.
> 
> I am not sure how 'push' side should be integrated, but I wish
> people could simply update a branch that is managed by foreign
> SCM interfaces such as git-svn and git-cvsimport with 'git fetch'
> by saying that the remote URL points at a non-git "repository"
> in remotes/ (or corresponding config).

> git-cvsimport builds the git objects from the changeset without
> using the working tree, and it would be very natural and simple
> to integrate it into 'git fetch', pretending as if it is just a
> funny transport.
> 
> If the interface uses the working tree to update the state from
> foreign SCM, then integrating with git-fetch would be
> inpractical.  I guess git-svn works that way?