| 1 |
On Thu, 24 May 2012 22:17:20 +1200 |
| 2 |
Kent Fredric <kentfredric@×××××.com> wrote: |
| 3 |
|
| 4 |
> On 24 May 2012 09:48, Michael Weber <xmw@g.o> wrote: |
| 5 |
> > -----BEGIN PGP SIGNED MESSAGE----- |
| 6 |
> > Hash: SHA256 |
| 7 |
> > |
| 8 |
> > On 05/23/2012 11:14 PM, Dan Douglas wrote: |
| 9 |
> >> On Wednesday, May 23, 2012 04:47:04 PM Robin H. Johnson wrote: |
| 10 |
> >>> 2. rsync generation is NOT going away. Users will still be using |
| 11 |
> >>> it. |
| 12 |
> > |
| 13 |
> > First, I'd stick with the current rsync to spread the tree (mirror |
| 14 |
> > work and mirrors+regular rsync users shouldn't notice any backend |
| 15 |
> > switch at all). |
| 16 |
> > |
| 17 |
> > |
| 18 |
> >> Would users have a way of gaining read-only access? This would be |
| 19 |
> >> EXTREMELY helpful. |
| 20 |
> > Sure, this would be possible like any other git checkout |
| 21 |
> > (layman-git-overlays, github.com, etc.). |
| 22 |
> > |
| 23 |
> > Please compare (browsing source and access description) |
| 24 |
> > http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/ |
| 25 |
> > http://git-exp.overlays.gentoo.org/gitweb/?p=exp/gentoo-x86.git |
| 26 |
> > |
| 27 |
> > |
| 28 |
> > - -- |
| 29 |
> > Gentoo Dev |
| 30 |
> > http://xmw.de/ |
| 31 |
> > -----BEGIN PGP SIGNATURE----- |
| 32 |
> > Version: GnuPG v2.0.17 (GNU/Linux) |
| 33 |
> > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
| 34 |
> > |
| 35 |
> > iF4EAREIAAYFAk+9W0EACgkQknrdDGLu8JADaQD+KC6cLJ5LqpNrKkNEBT1kAvJW |
| 36 |
> > xn+ZcfcMGJzc8GPyQZAA/jKug+5/DlDAHVGBIjAJOi9xf4EFqroL4eyPY8SD2neh |
| 37 |
> > =dvFZ |
| 38 |
> > -----END PGP SIGNATURE----- |
| 39 |
> > |
| 40 |
> |
| 41 |
> |
| 42 |
> I think there should most definitely be an official github mirror of |
| 43 |
> the main tree, just a "read-only" mirror from githubs perspective. |
| 44 |
> |
| 45 |
> Just how to best do the mirroring is the question |
| 46 |
> |
| 47 |
> a) Replicate to github when a user does 'push' with a server-side |
| 48 |
> push hook? ( Downside: if github goes down, gentoo devs will see it |
| 49 |
> when they push, and pushing takes longer because the output from the |
| 50 |
> replicated push is delivered to the original dev ) |
| 51 |
> |
| 52 |
> b) Daemonized hook that monitors for changes in the master repo, and |
| 53 |
> replicates commits to github after each push |
| 54 |
> |
| 55 |
> c) Tie it with the rsync tree building system so every time the tree |
| 56 |
> is built for rsync clients, the master is replicated to github. |
| 57 |
|
| 58 |
d) Talk with github folks to add our repo as 'mirror'. |
| 59 |
|
| 60 |
-- |
| 61 |
Best regards, |
| 62 |
Michał Górny |
Archives