[Pkg-e-devel] eina git-svn import pushed to git.debian.org

[Nikita V. Youshchenko]

> Because of that, I suggest not to use git-svn in local repos at all.
> Instead, set up cron job on alioths do update svn imports there every
> hour or so. And then use only git fetch to get svn/* updates into local
> repos.
>
> What do you think? I may try to set up that for eina ...

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?

- Upstream-vcs branch already exists in some repos - so while setting this 
up, existing branch will suffer non-fast-forward update. We agree?

- 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 doubt that pkg-e-commits mailing list should receive updates for 
upstream-vcs branch - it is going to have several updates per day.

- Under which account the script should run on alioth?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://lists.alioth.debian.org/pipermail/pkg-e-devel/attachments/20090125/7468bfa4/attachment.pgp