On Sun, Sep 14, 2014 at 2:03 PM, Michał Górny <mgo...@gentoo.org> wrote: > We have main developer repo where developers work & commit and are > relatively happy. For every push into developer repo, automated magic > thingie merges stuff into user sync repo and updates the metadata cache > there.
How long does the md5-cache regeneration process take? Are you sure it will be able to keep up with the rate of pushes to the repo during "peak hours"? If not, maybe we could use a time-based thing similar to the current cvs->rsync synchronization. [...] > Main developer repo > ------------------- > > I was able to create a start git repository that takes around 66M > as a git pack (this is how much you will have to fetch to start working > with it). The repository is stripped clean of history and ChangeLogs, > and has thin Manifests only. > > This means we don't have to wait till someone figures out the perfect > way of converting the old CVS repository. You don't need that history > most of the time, and you can play with CVS to get it if you really do. +1 > In any case, we would likely strip the history anyway to get a small > repo to work with. > > I have prepared a basic git update hook that keeps master clean > and attached it to the bug [1]. It enforces basic policies, prevents > forced updates and checks GPG signatures on left-most history line. It > can also be extended to do more extensive tree checks. Are we going to disallow merge commits and ask devs to rebase local changes in order to keep the history "clean"? Thanks a lot, Davide
