Bug 28261 - Repository migration to Git
Summary: Repository migration to Git
Alias: None
Product: Portland
Classification: Unclassified
Component: Portland (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Fathi Boudra
QA Contact:
Depends on:
Reported: 2010-05-26 07:54 UTC by Pablo Castellano (pablog)
Modified: 2010-12-31 01:45 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Description Pablo Castellano (pablog) 2010-05-26 07:54:43 UTC
I am opening this bugreport to track the status of the migration to Git.
I was said by Fabo that the migration was planned after the 1.0.3 release but I think we could do it sooner.

The thing is that for me is very uncomfortable looking into the commits with CVS and so, I have migrated the repository to Git for my own use but you can find it and see it here:

For the moment I will try to keep it merged with the CVS and so, people can fork it and work with Git.
Comment 1 Pablo Castellano (pablog) 2010-05-26 07:57:20 UTC
For the migration, the name and email of the committers/authors of patches could be rewritten to look prettier.

Should we contact all of them to ask how they want their name/email address?
This is the list:

$ git log|grep Author|sort |uniq -c
    232 Author: bastian <bastian>
      7 Author: bryce <bryce>
     57 Author: fabo <fabo>
      1 Author: jwhite <jwhite>
     26 Author: krake <krake>
     30 Author: llunak <llunak>
      3 Author: micke <micke>
      3 Author: mr <mr>
      9 Author: norbertf <norbertf>
     24 Author: rdieter <rdieter>
     85 Author: whipple <whipple>
Comment 2 Pablo Castellano (pablog) 2010-05-26 07:59:20 UTC
Forgot to say, if you want to import by yourself the CVS as Git, just run:

git cvsimport -d:pserver:anoncvs@anoncvs.freedesktop.org:/cvs/portland -k -v -C portland.git portland

It took to me ~48 minutes.
Comment 3 Fathi Boudra 2010-12-31 01:45:18 UTC

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.