From: merlyn@stonehenge.com (Randal L. Schwartz)
To: git@vger.kernel.org
Subject: tracking many cvs/svn/git remote archives
Date: 20 Nov 2006 09:18:05 -0800 [thread overview]
Message-ID: <86y7q6m3zm.fsf@blue.stonehenge.com> (raw)
Now that git-cvsimport and git-svn are mature, I'll share my script which I
call "get.cvs" to track a number of remote archives. It's not extremely
general, but maybe it'll inspire someone else to generalize it.
I have ~/MIRROR/foo-GITSVN tracking a remote archive using git-svn, so
the name of the directory reflects the tracking mechanism. There's also
*-CVS, *-SVN, *-GIT, and *-GITCVS.
For *-GITCVS, I have to keep the args for git-cvsimport around, so I
store that in the respository under getcvs.gitcvsargs.
For *-GITSVN, I have to force the head/origin to softlink to the proper remote
svn reference.
The *-GIT* merges are safe, because they won't pull over any uncommited
entries, but they *will* merge into whatever the current branch is. This
keeps any checked out tree trivially up to date, which is mostly what I'm
watching anyway.
Setting up *-GIT* generally requires checking out a master branch to really
track the files... I think I did this with "git-checkout -b master origin".
#!/bin/sh
cd && cd MIRROR || exit 1
case $# in
0) set -- '*';;
esac
eval set -- "$@"
trap ':' 2
for i in "$@"
do (
trap - 2
cd $i || exit
echo == $i ==
case $i in
*-CVS) cvs -q update;;
*-SVN) svn update;;
*-GIT*)
## first, update "origin":
case $i in
*-GIT)
git-fetch
;;
*-GITCVS)
git-cvsimport -k -i $(git-repo-config getcvs.gitcvsargs)
;;
*-GITSVN)
## be sure to have origin "ref: refs/remotes/git-svn"
git-svn multi-fetch
;;
esac
if git-status | grep -v 'nothing to commit'
then echo UPDATE SKIPPED
else
if git-pull . origin | egrep -v 'up-to-date'
then
git log --no-merges ORIG_HEAD.. | git shortlog
fi
fi
;;
*)
echo "[ignoring]";;
esac
)
done
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
next reply other threads:[~2006-11-20 17:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 17:18 Randal L. Schwartz [this message]
2006-11-21 14:57 ` remotes/* for "foreign" archives (was Re: tracking many cvs/svn/git remote archives) Randal L. Schwartz
2006-11-21 15:13 ` remotes/* for "foreign" archives Seth Falcon
2006-11-21 16:53 ` Randal L. Schwartz
2006-11-21 19:33 ` Junio C Hamano
2006-11-21 20:42 ` Petr Baudis
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=86y7q6m3zm.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.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 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.