git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Tracking and committing back to Subversion?

From
BSBrian Smith <linuxfood@linuxfood.net>
Date
Feb 4, 2006, 15:27 UTC
Message-ID
<200602040727.30965.linuxfood@linuxfood.net>
In-Reply-To
<1138834301.21899.40.camel@wilber.wgtn.cat-it.co.nz>
Well..
On Wednesday 01 February 2006 14:51, Sam Vilain wrote:
Show 5 quoted lines
> 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. )

Show 8 quoted lines
>      <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.)

Previous: Sam VilainNext: Sam Vilain
Message 5 of 12 in “Tracking and committing back to Subversion?”
  1. Sam VilainFeb 1, 2006
  2. Eric WongFeb 4, 2006
  3. Seth FalconFeb 4, 2006
  4. Sam VilainFeb 6, 2006
  5. Brian SmithFeb 4, 2006
  6. Sam VilainFeb 6, 2006
  7. Brian SmithFeb 10, 2006
  8. Junio C HamanoFeb 10, 2006
  9. Brian SmithFeb 10, 2006
  10. Sam VilainFeb 10, 2006
  11. Brian SmithFeb 10, 2006
  12. Sam VilainFeb 10, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.