All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Raymond <esr@thyrsus.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>,
	Sverre Rabbelier <srabbelier@gmail.com>,
	Avery Pennarun <apenwarr@gmail.com>,
	Jonathan Nieder <jrnieder@gmail.com>,
	Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Daniel Barkalow <barkalow@iabervon.org>,
	Peter Baumann <waste.manager@gmx.de>,
	Ilari Liusvaara <ilari.liusvaara@elisanet.fi>,
	Dave Olszewski <cxreg@pobox.com>,
	Christian Couder <chriscool@tuxfamily.org>,
	Steven Michalske <smichalske@gmail.com>,
	Jakub Narebski <jnareb@gmail.com>
Subject: Re: native-git-svn: A Summer of Code 2010 proposal
Date: Sun, 28 Mar 2010 08:10:34 -0400	[thread overview]
Message-ID: <20100328121034.GC25402@thyrsus.com> (raw)
In-Reply-To: <f3271551003280225v17af30d4s6d3d24b4d548ff7d@mail.gmail.com>

Ramkumar Ramachandra <artagnon@gmail.com>:
> Project Proposal: git-remote-svn | Native SVN support in Git
> Student: Ramkumar Ramachandra
> Mentor: Sverre Rabbelier

+1

I've just been through a Subversion-to-git migration, and have been
directly affected by an inadequacy in git-svn - failure to recognizer
SVN tags as tags rather than branches. See my blog post at
<http://esr.ibiblio.org/?p=1806>, "Subversion to GIT Migration: A Tale
of Two Gotchas" for discussion.

Accordingly, I support Ramkumar's proposal to rethink and rewrite the 
Subversion interface.  A concerted effort to do seamless interoperability 
would be well justified given the ubiquity of Subversion.  I think Rankumar
has chosen a goal that is useful, well defined, and realistically scoped.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

  parent reply	other threads:[~2010-03-28 12:10 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-27  5:40 native-git-svn: A Summer of Code 2010 proposal Steven Michalske
2010-03-27  6:46 ` Ramkumar Ramachandra
2010-03-27  8:03   ` Steven Michalske
2010-03-27  9:19 ` Eric Raymond
     [not found]   ` <f3271551003280225v17af30d4s6d3d24b4d548ff7d@mail.gmail.com>
2010-03-28 12:10     ` Eric Raymond [this message]
2010-03-29 20:04       ` Ramkumar Ramachandra
  -- strict thread matches above, loose matches on Subject: below --
2010-03-19 17:18 Ramkumar Ramachandra
2010-03-19 18:32 ` Avery Pennarun
2010-03-19 18:39   ` Sverre Rabbelier
2010-03-19 21:30     ` Avery Pennarun
2010-03-20  9:19       ` Ramkumar Ramachandra
2010-03-20 10:48       ` Johannes Schindelin
2010-03-20 20:34         ` Ramkumar Ramachandra
2010-03-20 20:55           ` Ramkumar Ramachandra
2010-03-20 21:04           ` Jonathan Nieder
2010-03-21 10:26             ` Johannes Schindelin
2010-03-21 11:08               ` Jonathan Nieder
2010-03-21 11:47                 ` Johannes Schindelin
2010-03-21 12:25                   ` Ramkumar Ramachandra
2010-03-21 12:31                     ` Johannes Schindelin
2010-03-21 12:36                     ` Sverre Rabbelier
2010-03-21 17:58                     ` Jonathan Nieder
2010-03-22  0:33                     ` Daniel Barkalow
2010-03-22  2:41                       ` Christian Couder
2010-03-22  3:49                         ` Ramkumar Ramachandra
2010-03-22 11:33                           ` Johannes Schindelin
     [not found]                             ` <f3271551003220643j3a726d09o2d3a078292fd8bf6@mail.gmail.com>
2010-03-22 19:52                               ` Johannes Schindelin
2010-03-23  7:49                                 ` Ramkumar Ramachandra
2010-03-20 21:58           ` Daniel Barkalow
2010-03-20 22:19             ` Ramkumar Ramachandra
2010-03-21  5:36             ` Ramkumar Ramachandra
2010-03-21 22:56               ` Daniel Barkalow
2010-03-21 17:08             ` Ilari Liusvaara
2010-03-21  7:40           ` Peter Baumann
2010-03-19 20:53   ` Jonathan Nieder
2010-03-19 21:00     ` Johannes Schindelin

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=20100328121034.GC25402@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=apenwarr@gmail.com \
    --cc=artagnon@gmail.com \
    --cc=barkalow@iabervon.org \
    --cc=chriscool@tuxfamily.org \
    --cc=cxreg@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=ilari.liusvaara@elisanet.fi \
    --cc=jnareb@gmail.com \
    --cc=jrnieder@gmail.com \
    --cc=smichalske@gmail.com \
    --cc=srabbelier@gmail.com \
    --cc=waste.manager@gmx.de \
    /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.