A script for keeping git up to date

[Eric Dantan Rzewnicki]

On Fri, May 07, 2010 at 02:25:02PM -0400, Eric Dantan Rzewnicki wrote:
> On Wed, May 05, 2010 at 10:09:31PM +0200, Reinhard Tartler wrote:
> > On Mon, May 03, 2010 at 00:55:43 (CEST), Felipe Sateler wrote:
> > > Ideas on how to make it faster are welcome (somehow finding out at
> > > once all the up to date repositories would be good). The script is
> > > specially slow in the best-case scenario (when all repositories are up
> > > to date). Also, it currently does not abort when a pull was not a fast
> > > forward, since gbp-pull does not return non-zero on that event. A bug
> > > has been filed against git-buildpackage.
> > > Finally, if some package has been removed from the pkg-multimedia
> > > area, it will not be removed from the local computer.
> > What I wonder is what's the correct workflow. Your script clones ever
> > pkg-multimedia git repository. Do you have numbers how much disk space
> > this takes? How much data needs to be transferred, and how long does git
> > need for that?
> 
> It took 65 minutes to get all of them here. Disk space about the same as
> Felipe's numbers.

Subsequent runs hang on the (empty) ladish repo. Should that be deleted,
or is someone still planning to package it?

-edrz