[Pkg-e-devel] eina git-svn import pushed to git.debian.org
albin.tonnerre at gmail.com
Sun Jan 25 21:31:39 UTC 2009
On Sun, Jan 25, 2009 at 01:07:41PM +0300, Nikita V. Youshchenko wrote :
> Or, even better, we may hide git-svn things on alioth. I mean, each pkg-e
> git repo on alioth will have svn/* 'remote branches' managed by git-svn.
> A cron job, executed hourly, will run
> git svn fetch
> git push . refs/remotes/svn/trunk:upstream-vcs
> in all repositories
> This will have an effect of having upstream-vcs branch in every repo, that
> automatically follows upstream svn. So pkg-e team could just forget about
> svn, and use only git :)
> Questions to answer before setting that up:
> - Do we agree with the idea?
Yes we do :)
> - Upstream-vcs branch already exists in some repos - so while setting this
> up, existing branch will suffer non-fast-forward update. We agree?
Seems unavoidable. I've had a hard time trying and failing to do that for eet,
as the cvs->svn move happened in the meantime. some libs were moved within the
svn at a later point, too
> - Somehow we should deny updates to upstream-vcs branch by anything other
> than this script, or things will likely break. How to do that?
I have no idea whatsoever. For now, I'd suggest a big fat warning and asking a
> - I doubt that pkg-e-commits mailing list should receive updates for
> upstream-vcs branch - it is going to have several updates per day.
If I read the hook script correctly, it discards all updates to
refs/remotes/* so that shouldn't be much of a problem.
> - Under which account the script should run on alioth?
I don't really mind, if you want to run it I'm fine with it, or I'll run it
under my user.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/pkg-e-devel/attachments/20090125/316ca1e0/attachment.pgp
More information about the Pkg-e-devel