From: Tzafrir Cohen <tzafrir.cohen@xorcom.com>
To: git@vger.kernel.org
Subject: git-svn with the asterisk svn repository
Date: Tue, 23 Jun 2009 10:55:00 +0300 [thread overview]
Message-ID: <20090623075500.GR3311@xorcom.com> (raw)
Hi
It took me quite a while to figure out how to use git-svn with the
repositories of the Asterisk project (now: http://svn.asterisk.org/svn/
). They have an extensive usage of svn:externals , which is changed from
branch to branch (mostly: "tagged" on a release tag) and thus using
submodules didn't seem useful.
Here are some notes of my workarounds.
Generally I tried to keep my the branches clean of unnecessary changes.
They need to build correctly without any need for extra changes. And for
the sake of clarity: even the gitignore file shouldn't be part of a
change. I want to be able to checkout a branch and just use it. Which
means that the gitignore file had to be on the gitignore file as well
and not checked in.
BTW: I also included a simple script to update the git tags from the SVN
"tags/*" branches (any such branch that matches a specific pattern and
for which a tag doesn't exist).
I also worked around the need of the svn:externals . Most of them were
for a common part of the build system called menuselect. I reimplemented
it in a single perl script and a very simple makefile (which are easy to
copy around). One or two other svn:exterernals don't seen to change
much, and I just used symlinks instead.
Simple documentation and scripts are available at
http://git.tzafrir.org.il/?p=asterisk-tools.git;a=tree
(Please CC replies if you actually want me to read them, as I almost
don't read this list)
P.S.: Anybody had luck with git-svn and HTTPS certificates
authentication recently? I never tried to use git-svn to commit
anything.
--
Tzafrir Cohen
icq#16849755 jabber:tzafrir.cohen@xorcom.com
+972-50-7952406 mailto:tzafrir.cohen@xorcom.com
http://www.xorcom.com iax:guest@local.xorcom.com/tzafrir
reply other threads:[~2009-06-23 8:18 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=20090623075500.GR3311@xorcom.com \
--to=tzafrir.cohen@xorcom.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;
as well as URLs for NNTP newsgroup(s).