Mass git migration

Kristian Høgsberg krh at
Thu Jun 29 12:29:01 PDT 2006

On 6/29/06, Alan Coopersmith <alan.coopersmith at> wrote:
> Kristian Høgsberg wrote:
> > Hello,
> >
> > I was pondering migrating a few modules to git, but I though we might
> > as well do this once and for all.  So I wrote the attached script to
> > automate the instructions on the git migration page:
> >
> >
> >
> > except the part about copying to kemper, which will require admin
> > rights.  Except for the automatic adding of AC_MSG_ERROR() to the
> >'s, the script doesn't touch the CVS repos at all.
> I noticed you don't even remove write permission:
>          # chmod -R a-w /cvs/xorg/$section/$module
> Wouldn't it be best to do this for at least the length of the migration
> so no one commits to CVS while you're in the middle of conversion?

Ah, I should have left a comment in the script about that.  I
commented it out while I was testing it, so I wouldn't make the cvs
repo readonly at that time.  Like the sed_repo and sed_module vars
further down in the script this need to be changed once I run it for

> Also, I see you have libs, app, proto & driver - are we going to leave
> docs, fonts, data & util in CVS?   ( data/xkbdata should not be migrated since
> we don't ever plan another release of it, but the bitmaps & cursors should
> move eventually.  Working with xkb-config to migrate the xlibs/xkb-desc to
> a non-dead SCM repository would be good but not part of this effort.)

We should move everything to git, I guess I just stopped setting up
migrations when I had all the code repositories done.  I'll add the
remaining cvs modules before doing the conversion.

> My one timing concern is wondering if there will be admins around Friday
> to do the final steps or if they'll all be at GUADEC still.   (Well, all
> except ajax - if he's willing to help, then there's no problem.)

Yeah, that's true.  I just pinged ajax, and he's around tomorrow and
can help copying the repositories over.


More information about the xorg mailing list