Re: native-git-svn: A Summer of Code 2010 proposal
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Mar 20, 2010, 10:48 UTC
- Message-ID
- <alpine.DEB.1.00.1003201148230.7596@pacific.mpi-cbg.de>
- In-Reply-To
- <32541b131003191430ld0eaa9cw1d2aac08cff15682@mail.gmail.com>
Hi,
On Fri, 19 Mar 2010, Avery Pennarun wrote:
Show 16 quoted lines
> On Fri, Mar 19, 2010 at 2:39 PM, Sverre Rabbelier <srabbelier@gmail.com> wrote: > > On Fri, Mar 19, 2010 at 19:32, Avery Pennarun <apenwarr@gmail.com> wrote: > >> - all those "extra commands" that git-svn supports are considered > >> backwards compatibility, even if they're absolutely obsolete because > >> of newer commands, and therefore will be very hard to justify getting > >> rid of > > > > I don't think this is true. The proposal is to implement > > git-remote-svn, which would allow _native_ interaction with svn > > repositories, so without using 'git svn'. It would allow 'git clone > > svn://example.com/myrepo' and subsequent "git pull"s from that svn > > source. Do you agree that makes (part of) your comments moot, or am I > > missing something? > > I don't know enough about the proposal to comment on this part of the > design.
How about reading it? It's on the Wiki.
Ciao, Dscho