Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Michał Górny <mgorny@g.o>
Subject: Re: Portage Git migration - clean cut or git-cvsserver
Date: Thu, 24 May 2012 16:40:02 +0200
On Thu, 24 May 2012 22:17:20 +1200
Kent Fredric <kentfredric@...> wrote:

> On 24 May 2012 09:48, Michael Weber <xmw@g.o> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA256
> >
> > On 05/23/2012 11:14 PM, Dan Douglas wrote:
> >> On Wednesday, May 23, 2012 04:47:04 PM Robin H. Johnson wrote:
> >>> 2. rsync generation is NOT going away. Users will still be using
> >>> it.
> >
> > First, I'd stick with the current rsync to spread the tree (mirror
> > work and mirrors+regular rsync users shouldn't notice any backend
> > switch at all).
> >
> >
> >> Would users have a way of gaining read-only access? This would be
> >> EXTREMELY helpful.
> > Sure, this would be possible like any other git checkout
> > (layman-git-overlays, github.com, etc.).
> >
> > Please compare (browsing source and access description)
> > http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/
> > http://git-exp.overlays.gentoo.org/gitweb/?p=exp/gentoo-x86.git
> >
> >
> > - --
> > Gentoo Dev
> > http://xmw.de/
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v2.0.17 (GNU/Linux)
> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
> >
> > iF4EAREIAAYFAk+9W0EACgkQknrdDGLu8JADaQD+KC6cLJ5LqpNrKkNEBT1kAvJW
> > xn+ZcfcMGJzc8GPyQZAA/jKug+5/DlDAHVGBIjAJOi9xf4EFqroL4eyPY8SD2neh
> > =dvFZ
> > -----END PGP SIGNATURE-----
> >
> 
> 
> I think there should most definitely be an official github mirror of
> the main tree, just a "read-only" mirror from githubs perspective.
> 
> Just how to best do the mirroring is the question
> 
> a) Replicate to github when a user does 'push' with a server-side
> push hook? ( Downside: if github goes down, gentoo devs will see it
> when they push, and pushing takes longer because the output from the
> replicated push is delivered to the original dev )
> 
> b) Daemonized hook that monitors for changes in the master repo, and
> replicates commits to github after each push
> 
> c) Tie it with the rsync tree building system so every time the tree
> is built for rsync clients, the master is replicated to github.

d) Talk with github folks to add our repo as 'mirror'.

-- 
Best regards,
Michał Górny
Attachment:
signature.asc (PGP signature)
Replies:
Re: Portage Git migration - clean cut or git-cvsserver
-- Ralph Sennhauser
References:
Portage Git migration - clean cut or git-cvsserver
-- Michael Weber
Re: Portage Git migration - clean cut or git-cvsserver
-- Dan Douglas
Re: Portage Git migration - clean cut or git-cvsserver
-- Michael Weber
Re: Portage Git migration - clean cut or git-cvsserver
-- Kent Fredric
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: Portage Git migration - clean cut or git-cvsserver
Next by thread:
Re: Portage Git migration - clean cut or git-cvsserver
Previous by date:
Re: Re: Portage Git migration - clean cut or git-cvsserver
Next by date:
Re: Portage Git migration - clean cut or git-cvsserver


Updated Jun 29, 2012

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.