All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: kusmabite@gmail.com, "Stephen Bash" <bash@genarts.com>,
	"Jonathan Nieder" <jrnieder@gmail.com>,
	"David Michael Barr" <david.barr@cordelta.com>,
	"Daniel Shahaf" <d.s@daniel.shahaf.name>,
	"Stefan Sperling" <stsp@elego.de>,
	"Bert Huijben" <rhuijben@collab.net>,
	"Will Palmer" <wmpalmer@gmail.com>,
	"Philip Martin" <philip.martin@wandisco.com>,
	"Jonas Gehring" <jonas.gehring@boolsoft.org>,
	"Ævar Arnfjörð" <avarab@gmail.com>,
	"Git Mailing List" <git@vger.kernel.org>
Subject: Re: [GSoC update] git-remote-svn: The final one
Date: Tue, 17 Aug 2010 22:48:49 +0530	[thread overview]
Message-ID: <20100817171846.GG6947@kytes> (raw)
In-Reply-To: <AANLkTim5RYDuius6Oa6KX0weQhwVz+_YP=1-ujb3-CuJ@mail.gmail.com>

Hi Sverre,

Sverre Rabbelier writes:
> Heya,
> 
> On Tue, Aug 17, 2010 at 11:10, Erik Faye-Lund <kusmabite@gmail.com> wrote:
> > On Tue, Aug 17, 2010 at 5:59 PM, Ramkumar Ramachandra
> > <artagnon@gmail.com> wrote:
> >> We're doing better than that- when the whole thing is complete, we
> >> should have perfectly seamless two-way compatibility.
> >
> > Does this include handling SVN repos where the layout have changed
> > during it's lifetime? If so, how will this look on the git side?
> 
> Perhaps it makes sense to start a new thread to hash that out for when
> the time comes to implement that?

Good idea. I've posted a new timeline. I'll put up some branch/ tag
mapper notes next week.

-- Ram

  reply	other threads:[~2010-08-17 17:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-17 14:42 [GSoC update] git-remote-svn: The final one Ramkumar Ramachandra
2010-08-17 15:48 ` Stephen Bash
2010-08-17 15:59   ` Ramkumar Ramachandra
2010-08-17 16:10     ` Erik Faye-Lund
2010-08-17 16:20       ` Sverre Rabbelier
2010-08-17 17:18         ` Ramkumar Ramachandra [this message]
2010-08-17 16:22       ` Ramkumar Ramachandra
2010-08-17 16:20     ` Stephen Bash
2010-08-17 16:41       ` Ramkumar Ramachandra

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100817171846.GG6947@kytes \
    --to=artagnon@gmail.com \
    --cc=avarab@gmail.com \
    --cc=bash@genarts.com \
    --cc=d.s@daniel.shahaf.name \
    --cc=david.barr@cordelta.com \
    --cc=git@vger.kernel.org \
    --cc=jonas.gehring@boolsoft.org \
    --cc=jrnieder@gmail.com \
    --cc=kusmabite@gmail.com \
    --cc=philip.martin@wandisco.com \
    --cc=rhuijben@collab.net \
    --cc=srabbelier@gmail.com \
    --cc=stsp@elego.de \
    --cc=wmpalmer@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.