git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bruno Cesar Ribas <ribas@c3sl.ufpr.br>
To: "Karl Hasselström" <kha@treskal.com>
Cc: Julian Phillips <julian@quantumfyre.co.uk>,
	"Shawn O. Pearce" <spearce@spearce.org>,
	git@vger.kernel.org
Subject: Re: Git / Subversion Interoperability
Date: Fri, 23 Mar 2007 12:21:02 -0300	[thread overview]
Message-ID: <20070323152102.GA4818@c3sl.ufpr.br> (raw)
In-Reply-To: <20070323103426.GA15923@diana.vm.bytemark.co.uk>

On Fri, Mar 23, 2007 at 11:34:26AM +0100, Karl Hasselström wrote:
> On 2007-03-23 01:36:11 +0000, Julian Phillips wrote:
> 
> > On Thu, 22 Mar 2007, Shawn O. Pearce wrote:
> >
> > > I thought about the properties, but didn't bother to write
> > > anything on that subject as we may just be able to say "look,
> > > properties are not supported in git-svnserver, so don't try to use
> > > them".
> >
> > Indeed. That's what I was aiming at with the the last sentence (not
> > very clearly unfortunately). It would be nice if the server could
> > tell the client that properties are not supported ... but I doubt
> > that it can, since they are fundamental part of Subversion.
> >
> > In particular it's how the client finds out about things like
> > symlinks and line ending conversion. It may be necessary to provide
> > some basic support for some of the properties in the svn:...
> > namespace in order for the Subversion repo access library not to
> > refuse to talk to the git server.
> 
> Maybe the pragmatic solution would be to have built-in handling of a
> few properties such as svn:executable and svn:ignore that have git
> equivalents, and just emulate all other properties with files.

My idea is to write the git-svnserver!!! I think it will be easier.

To begin coding, i plan to write basic functions [updade,commit,checkout,
copy,merge,...] then start to implement most "complex" instructions.

As spearce said before, the idea of this is to migrate from svn to git
without many trouble in transition, so basic can work as the initial thought.

> 
> -- 
> Karl Hasselström, kha@treskal.com
>       www.treskal.com/kalle

-- 
Bruno Ribas - ribas@c3sl.ufpr.br
http://web.inf.ufpr.br/ribas
C3SL: http://www.c3sl.ufpr.br 

  reply	other threads:[~2007-03-23 15:21 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-22 22:48 Git / Subversion Interoperability Bruno Cesar Ribas
2007-03-23  0:43 ` Shawn O. Pearce
2007-03-23  1:03   ` Julian Phillips
2007-03-23  1:24     ` Shawn O. Pearce
2007-03-23  1:36       ` Julian Phillips
2007-03-23 10:34         ` Karl Hasselström
2007-03-23 15:21           ` Bruno Cesar Ribas [this message]
2007-03-23 15:48             ` Karl Hasselström
2007-03-23 18:13             ` Julian Phillips
2007-03-23 19:34               ` Bruno Cesar Ribas
2007-03-23 22:05                 ` David Lang
2007-03-23 22:11                 ` Daniel Barkalow
2007-03-24  6:41           ` Shawn O. Pearce
2007-03-24 18:55             ` Karl Hasselström
2007-03-24 20:13               ` Linus Torvalds
2007-03-24 20:37                 ` Junio C Hamano
2007-03-26  3:06             ` Sam Vilain
2007-03-23 21:30     ` Christian Wiese
2007-03-23 22:00       ` Steven Grimm
2007-03-24  6:56         ` Shawn O. Pearce
2007-03-26  3:04           ` Sam Vilain
2007-03-23 14:21   ` Jakub Narebski
2007-03-24  6:45     ` Shawn O. Pearce
2007-03-24 20:38       ` Eric Wong
2007-03-24 20:31 ` Eric Wong

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=20070323152102.GA4818@c3sl.ufpr.br \
    --to=ribas@c3sl.ufpr.br \
    --cc=git@vger.kernel.org \
    --cc=julian@quantumfyre.co.uk \
    --cc=kha@treskal.com \
    --cc=spearce@spearce.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.
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 NNTP newsgroup(s).