From: Stefano Zacchiroli <zack@upsilon.cc>
To: git@vger.kernel.org
Subject: rfc on a svn -> git wrapper script
Date: Tue, 18 Mar 2008 16:24:27 +0100 [thread overview]
Message-ID: <20080318152427.GA2219@takhisis.invalid> (raw)
Hi all,
I want to convert a medium-sized subversion repository [1] to several
git repositories. In doing so I've a couple of extra requirements which
are not directly handled by git-svn. The main ones are:
- get rid of old .orig.tar.gz tarballs which have been commited in the
past to the repo
- get rid of the git-svn metadata as the conversion will be one-way and
will happen only once
- make the repository bare
- convert old subversion tags to real git tags
(BTW, I'm quite surprised git-svn doesn't do that, but I understand
that there are no guarantees that tags on the subversion side have
been used as such ...)
As a side goal I need all this to be made easy for people which know
potentially nothing about git (they will start learning when the
conversions have been done).
Hence, to automate the above stuff I've made a helper script [2] (with a
companion of him, which is way less interesting [3]).
Since I'm quite new to git, and given that some stuff (e.g. removing the
tarballs and ensuring their space can be reclaimed back) is quite
tricky, I was wondering if someone can have a look at the script to
check if I've overlooked something obvious or not ...
Comments will be very much appreciated,
Many thanks in advance!
[1] svn://svn.debian.org/pkg-ocaml-maint/
[2] http://svn.debian.org/viewsvn/pkg-ocaml-maint/trunk/tools/svn2git/svn2git_alioth?view=markup
[3] http://svn.debian.org/viewsvn/pkg-ocaml-maint/trunk/tools/svn2git/svn2git_pkg-ocaml-maint?view=markup
--
Stefano Zacchiroli -*- PhD in Computer Science ............... now what?
zack@{upsilon.cc,cs.unibo.it,debian.org} -<%>- http://upsilon.cc/zack/
(15:56:48) Zack: e la demo dema ? /\ All one has to do is hit the
(15:57:15) Bac: no, la demo scema \/ right keys at the right time
reply other threads:[~2008-03-19 21:58 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=20080318152427.GA2219@takhisis.invalid \
--to=zack@upsilon.cc \
--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;
as well as URLs for NNTP newsgroup(s).