Re: [PATCH 4/5] Draft of API for git-vcs-*, transport.c code to use it.

> On Wed, 25 Mar 2009, Junio C Hamano wrote:
>
>> Suppose a project used to use subversion, but it migrated to git (not an
>> unheard-of scenario these days, I hope).  The git repository now is the
>> authoritative one, all the development happens on this side.
>> 
>> But in order to help:
>> 
>>  - people who have established their workflow to follow the project
>>    (e.g. not necessarily contributing anything back, but just doing
>>    regular "svn update");
>> 
>>  - people who have leftover local changes from the subversion days; and
>> 
>>  - other project infrastracture (e.g. trac) that the project hasn't
>>    managed to interface to the new git repository yet;
>> 
>> the project decides to keep feeding recent updates to the subversion
>> repository that used to be authoritative, even though it is now declared
>> read-only (i.e. the only update comes from the git end).
>
> Actually, this is easy: just configure the git repo to not fetch anything 
> from the no-longer-authoritative subversion repository. git-vcs-svn would 
> waste a bunch of time reimporting what it exported, but it wouldn't 
> actually do anything with it (since it doesn't even have tracking refs to 
> update). It could, of course, be optimized to avoid reimporting if it 
> doesn't need to.