From: Sam Vilain <sam@vilain.net>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: "Karl Hasselström" <kha@treskal.com>,
"Julian Phillips" <julian@quantumfyre.co.uk>,
"Bruno Cesar Ribas" <ribas@c3sl.ufpr.br>,
git@vger.kernel.org
Subject: Re: Git / Subversion Interoperability
Date: Mon, 26 Mar 2007 15:06:51 +1200 [thread overview]
Message-ID: <460738CB.2050707@vilain.net> (raw)
In-Reply-To: <20070324064130.GC25863@spearce.org>
Shawn O. Pearce wrote:
> That is not a bad idea at all. We could easily do
>
> svn:executable -> (mode & 0111);
> svn:ignore -> .gitignore;
>
> I'm sure there are others, but they are the only two Karl mentioned,
> and that I know of off the top of my head. ;-)
>
> Additional random properties could just be written out to .gitsvnprop
> in the parent directory.
>
There are also the important properties "svk:merge" and "svnmerge",
which allow you to notate when a revision has an extra parent. SVK
and/or svnmerge should then be able to use the extra merge information
without any extra work. Additionally, people might want to push back
with these properties.
Sam.
next prev parent reply other threads:[~2007-03-26 3:06 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
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 [this message]
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=460738CB.2050707@vilain.net \
--to=sam@vilain.net \
--cc=git@vger.kernel.org \
--cc=julian@quantumfyre.co.uk \
--cc=kha@treskal.com \
--cc=ribas@c3sl.ufpr.br \
--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).