From: Markus Schaber <m.schaber@codesys.com>
To: "esr@thyrsus.com" <esr@thyrsus.com>, Daniel Shahaf <danielsh@elego.de>
Cc: "dev@subversion.apache.org" <dev@subversion.apache.org>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: AW: reposurgeon now writes Subversion repositories
Date: Thu, 29 Nov 2012 13:43:06 +0000 [thread overview]
Message-ID: <727D8E16AE957149B447FE368139F2B50D9951CB@SERVER10> (raw)
In-Reply-To: <20121129114637.GB9264@thyrsus.com>
Hi,
Von: Eric S. Raymond [mailto:esr@thyrsus.com]
> > How does reposurgeon handle empty directories with (node) properties?
>
> Currently by ignoring all of them except svn:ignore, which it turns
> into .gitignore content on the gitspace side. And now vice-versa, too.
>
> Not clear what else it *could* do. I'd take suggestions.
AFAIR, SvnBridge (which bridges SVN to Team Foundation Server for CodePlex) creates a hidden .svnproperties file where all the properties of the directory and files are stored.
I'm not really sure, but maybe this could be used as some standard to bridge svn properties to non-svn VCSes.
Best regards
Markus Schaber
CODESYS(r) a trademark of 3S-Smart Software Solutions GmbH
Inspiring Automation Solutions
3S-Smart Software Solutions GmbH
Dipl.-Inf. Markus Schaber | Product Development Core Technology
Memminger Str. 151 | 87439 Kempten | Germany
Tel. +49-831-54031-979 | Fax +49-831-54031-50
E-Mail: m.schaber@codesys.com | Web: http://www.codesys.com
CODESYS internet forum: http://forum.codesys.com
Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915
prev parent reply other threads:[~2012-11-29 13:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-29 5:59 reposurgeon now writes Subversion repositories Eric S. Raymond
2012-11-29 7:58 ` Daniel Shahaf
2012-11-29 10:31 ` Branko Čibej
2012-11-29 11:46 ` Eric S. Raymond
2012-11-29 13:42 ` Daniel Shahaf
2012-11-29 13:55 ` Eric S. Raymond
2012-11-29 13:43 ` Markus Schaber [this message]
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=727D8E16AE957149B447FE368139F2B50D9951CB@SERVER10 \
--to=m.schaber@codesys.com \
--cc=danielsh@elego.de \
--cc=dev@subversion.apache.org \
--cc=esr@thyrsus.com \
--cc=git@vger.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox