From: Brian Smith <linuxfood@linuxfood.net>
To: sam@vilain.net
Cc: git@vger.kernel.org
Subject: Re: Tracking and committing back to Subversion?
Date: Sat, 4 Feb 2006 07:27:25 -0800 [thread overview]
Message-ID: <200602040727.30965.linuxfood@linuxfood.net> (raw)
In-Reply-To: <1138834301.21899.40.camel@wilber.wgtn.cat-it.co.nz>
[-- Attachment #1: Type: text/plain, Size: 1130 bytes --]
Well..
On Wednesday 01 February 2006 14:51, Sam Vilain wrote:
> Hi all,
>
> Has anyone done any work on bidirectional access to SVN repositories?
> ie, tracking and committing.
>
I'm working on something that does just that, I haven't gotten to the
bidirectional part just yet. (The only reason I didn't use git-svnimport is
that it has a /terrible/ time importing from the KDE svn repo. )
> <prop-dir> is a directory object, with one file in this example;
> called svn:ignore. The contents of this file would be something
> like the .gitignore;
>
> Makefile
> Makefile.old
> blib
> ...etc...
My take on the properties, though I like your thoughts on how to handle at
least svn:ignore, is to basically just let svn deal with them. I will make a
couple tools that will modify them, for interface reasons, but they'll just
be wrappers around the svn commands themselves.
At the moment, the tools are written as bash shell scripts with an interface
I'm trying to keep as intuitive as cogito (even though I use the core-git
tools now.)
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-02-04 15:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 22:51 Tracking and committing back to Subversion? Sam Vilain
2006-02-04 5:40 ` Eric Wong
2006-02-04 19:51 ` Seth Falcon
2006-02-06 23:12 ` Sam Vilain
2006-02-04 15:27 ` Brian Smith [this message]
2006-02-06 23:23 ` Sam Vilain
2006-02-10 0:50 ` Brian Smith
2006-02-10 0:54 ` Junio C Hamano
2006-02-10 1:06 ` Brian Smith
2006-02-10 4:27 ` Sam Vilain
2006-02-10 7:01 ` Brian Smith
2006-02-10 11:16 ` Sam Vilain
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=200602040727.30965.linuxfood@linuxfood.net \
--to=linuxfood@linuxfood.net \
--cc=git@vger.kernel.org \
--cc=sam@vilain.net \
/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.