Re: [gentoo-dev] proxy maintainership and gentoo-x86 scm

[Nirbheek Chauhan <nirbheek@gentoo.org>]

On Fri, Jan 15, 2010 at 4:24 AM, Robin H. Johnson <robbat2@gentoo.org> wrote:
> On Fri, Jan 15, 2010 at 03:59:00AM +0530, Nirbheek Chauhan wrote:
>> ChangeLog (-13,000 which would be redundant, and should be
>> auto-generated alongwith metadata prior to distribution via rsync.
>> Hey, this is something that needs to be done too!)
> ChangeLog != commit logs.
>
> There is frequently additional information in the CVS commit messages
> that isn't in the ChangeLogs. ChangeLogs aren't always updated reliably
> either, esp for ebuild cleanups (hi vapier).
>

All the more reason to just chuck manual ChangeLogs in favour of
auto-generated ones. Atleast, that's what gnome projects do since they
moved to git [ http://live.gnome.org/Git/ChangeLog ].

However, this will entail a change in how commit messages are
formatted; git commit messages need to be very different from CVS/svn
ones.

> The actual performance of git itself isn't the largest problem.
> The migration issues, esp. the speed of the conversion are.
>
> My status of the migration side itself hasn't changed since the end of
> October:
> http://archives.gentoo.org/gentoo-scm/msg_e0a0a41200c1fc6a0fda68b4ff9d2c61.xml
>
> That top item is the largest blocker. The actual conversion time is down
> to 9 hours, but with more than that again in setting it up. I'd like to
> get the conversion time down to UNDER 4 hours. It's mostly
> single-threaded, and we've got lots of cores available, it just needs
> parallelization. We're basically dead in the water during the
> conversion, there is NO incremental support at all.
>

Actually, this has confused me for a while. Sorry if this is a dumb
question, but why do we care about the conversion speed if we can just
convert it once, make the old cvs repo read-only and be done with it?
Are we concerned about the window during which cvs access will have to
be blocked and devs will sit around twiddling thumbs?

> Side-project to the above: Is there anything link Psyco for Python
> acceleration that works on 64-bit machines? Psyco itself has a warning
> on the frontpage of no 64-bit support.
>

I had written Pysco off as dead and started looking forward to Unladen
Swallow :)

http://code.google.com/p/unladen-swallow/wiki/ProjectPlan

> We DO still need somebody that cares about CVS access to test with
> git-cvssserver against the existing conversion.
>

This will fit in quite badly with the proposed changes to make
Manifest have only distfile manifests when using git, and to not have
ChangeLogs for the simple reason that they (Manifests and ChangeLogs)
invariably cause merge conflicts. And then there was also the plan to
not edit headers for files to prevent extra commits (which are even
more useless in git).


-- 
~Nirbheek Chauhan

Gentoo GNOME+Mozilla Team