All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Wong <normalperson@yhbt.net>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>,
	Git Mailing List <git@vger.kernel.org>,
	David Michael Barr <david.barr@cordelta.com>,
	Sverre Rabbelier <srabbelier@gmail.com>,
	"Shawn O. Pearce" <spearce@spearce.org>,
	Daniel Shahaf <d.s@daniel.shahaf.name>
Subject: Re: [GSoC update extra!] git-remote-svn: Week 8
Date: Thu, 24 Jun 2010 14:32:04 -0700	[thread overview]
Message-ID: <20100624213204.GA22756@dcvr.yhbt.net> (raw)
In-Reply-To: <20100624180752.GA1642@burratino>

Jonathan Nieder <jrnieder@gmail.com> wrote:
> [1] Eric, we are discussing the remote-svn series[2] and especially
> Ram, Sverre, and David’s recent comments[3].  Apologies for not
> keeping you in the loop sooner; your insights have always been
> helpful in the past.

No worries Jonathan, I've been preoccupied with several other projects,
none of which require dealing with SVN :)

> As for the idea of reimplementing git-svn on top of svn-fe: yes, the
> fast-import stream would need more information to support
> --follow-parent, but that piece is not so hard to add AFAICT.  Of
> course, I am mentioning this not because it is important to keep the
> git-svn interface but because the --stdlayout feature is very useful
> and we may want to port it over some day.

Yes, I've always found --stdlayout very convenient and hope it
lives on.

-- 
Eric Wong

  reply	other threads:[~2010-06-24 21:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-24 13:33 [GSoC update extra!] git-remote-svn: Week 8 Ramkumar Ramachandra
2010-06-24 17:39 ` Jonathan Nieder
2010-06-24 18:07   ` Jonathan Nieder
2010-06-24 21:32     ` Eric Wong [this message]
2010-06-30  1:51     ` Sam Vilain
2010-06-30 12:45       ` Ramkumar Ramachandra
2010-07-01  3:38         ` Sam Vilain
2010-06-30  2:20   ` Sam Vilain

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=20100624213204.GA22756@dcvr.yhbt.net \
    --to=normalperson@yhbt.net \
    --cc=artagnon@gmail.com \
    --cc=d.s@daniel.shahaf.name \
    --cc=david.barr@cordelta.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=spearce@spearce.org \
    --cc=srabbelier@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.