Git development
 help / color / mirror / Atom feed
From: "Art Haas" <ahaas@airmail.net>
To: git@vger.kernel.org
Subject: Working with git-svn to export changes to Subversion
Date: Mon, 28 May 2007 15:27:12 -0500	[thread overview]
Message-ID: <20070528202712.GA11207@artsapartment.org> (raw)

Hi.

A few days ago I posted a message to this list regarding my attempts to
convert the PythonCAD Subversion repository into git. My first efforts
failed, but after several more attempts and some editing of the
git-svnimport code I've been able to convert the entire repo, tags and
all, seemingly successfully.

Having now converted my repo, I'm now tackling the second-half of my
task, which is to figure out how to use 'git-svn' to export my changes
to a Subversion repository. The documentation for 'git-svn' is set up
to guide someone using git to track a project kept in Subversion, where
in my case the code will be kept in git and exported out into
Subversion. I plan on pushing my changes solely to 'trunk', and when
I make a release I want to tag it and push the tag into the Subversion
repository as well.

I'm writing today to see if others using 'git-svn' are currently using
it in the form I'm trying to do, and if so could these people give me a
couple of pointers regarding any tips, tricks, and/or pitfalls that I
may encounter. Thanks in advance for any info you can send my direction.

My thanks also go to everyone that has contributed to the 'git-svnimport'
code, and git itself as well.

Art Haas
-- 
Man once surrendering his reason, has no remaining guard against absurdities
the most monstrous, and like a ship without rudder, is the sport of every wind.

-Thomas Jefferson to James Smith, 1822

                 reply	other threads:[~2007-05-28 20:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20070528202712.GA11207@artsapartment.org \
    --to=ahaas@airmail.net \
    --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