From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Julian Phillips <julian@quantumfyre.co.uk>
Cc: Jakub Narebski <jnareb@gmail.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
Robin Rosenberg <robin.rosenberg.lists@dewire.com>,
git@vger.kernel.org, John Hawley <warthog9@kernel.org>
Subject: Re: Google Summer of Code 2008
Date: Fri, 29 Feb 2008 13:03:15 +0000 (GMT) [thread overview]
Message-ID: <alpine.LSU.1.00.0802291302560.22527@racer.site> (raw)
In-Reply-To: <Pine.LNX.4.64.0802291241400.18516@reaper.quantumfyre.co.uk>
Hi,
On Fri, 29 Feb 2008, Julian Phillips wrote:
> On Fri, 29 Feb 2008, Jakub Narebski wrote:
>
> > * Git / Subversion Interoperability
> >
> > The idea here is implement something in Git that speaks the Subversion
> > protocol on the wire, but uses Git as the backend storage. (This would
> > be like the existing git-cvsserver.)
> >
> > There are two potential approaches:
> >
> > 1. git-svnserver
> > 2. write a backend for Subversion
> >
> > Goal: To be able to access git repository, at minimum read-only, from
> > a Subversion client, at least svn CLI.
> > Language: Open for proposal.
> > Suggested mentors:
> > Eric Wong (git-svn author)
> > Matthias Urlichs (git-svnimport author)
> > Notes: I don't think we could pass it as Subversion SoC project, but
> > I guess that we could ask for co-mentor for the Subversion protocol,
> > or Subversion backend part of this task.
>
> FWIW: I have a partially implemented python git-svnserver that speaks the
> svn:// protocol ... so far I can checkout from a git repos using the svn
> client, and not much else. It's been on the backburner for a while, but I had
> recently thought about revisiting it - but getting someone else to do the
> implementation works too ;)
How about publishing it, so other people can take up the ball?
Ciao,
Dscho
next prev parent reply other threads:[~2008-02-29 13:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 22:56 Google Summer of Code 2008 Jakub Narebski
2008-02-26 23:39 ` Johannes Schindelin
2008-02-28 6:36 ` Shawn O. Pearce
2008-02-28 7:03 ` Jeremy Maitin-Shepard
2008-02-28 10:27 ` Johannes Schindelin
2008-02-28 10:27 ` Johannes Schindelin
2008-02-29 12:04 ` Jakub Narebski
2008-02-29 12:47 ` Julian Phillips
2008-02-29 13:03 ` Johannes Schindelin [this message]
2008-03-01 1:37 ` Julian Phillips
2008-03-01 0:31 ` Sam Vilain
2008-03-01 1:03 ` Johannes Schindelin
2008-03-01 5:07 ` Sam Vilain
2008-03-01 23:53 ` Jakub Narebski
2008-03-02 16:05 ` Matthieu Moy
2008-03-02 16:46 ` Jakub Narebski
2008-03-02 18:05 ` Matthieu Moy
2008-03-02 23:04 ` Martin Langhoff
2008-03-02 23:35 ` Johannes Schindelin
2008-02-28 13:59 ` Jonas Fonseca
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LSU.1.00.0802291302560.22527@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=julian@quantumfyre.co.uk \
--cc=robin.rosenberg.lists@dewire.com \
--cc=spearce@spearce.org \
--cc=warthog9@kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).