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
<p><br>
On May 23, 2012 1:55 PM, "Johannes Huber" <<a href="mailto:johu@g.o">johu@g.o</a>> wrote:<br>
><br>
> Am Mittwoch 23 Mai 2012, 14:42:37 schrieb Michael Weber:<br>
><br>
> > -----BEGIN PGP SIGNED MESSAGE-----<br>
><br>
> > Hash: SHA256<br>
><br>
> ><br>
><br>
> > Hi,<br>
><br>
> ><br>
><br>
> > i've looked at the blockers of "[TRACKER] portage migration to git"<br>
><br>
> > [1] and want to discuss "testing git-cvsserver" [2].<br>
><br>
> ><br>
><br>
> > There are two proposed scenarios how to migrate the developers write<br>
><br>
> > access to the portage tree.<br>
><br>
> ><br>
><br>
> > "Clean cut" turns of cvs access on a given and announced timestamp,<br>
><br>
> > rsync-generation/updates is suspended (no input -> no changes), some<br>
><br>
> > magic scripts prepare the git repo (according to [3], some hours<br>
><br>
> > duration) and we all checkout the tree (might be some funny massive load).<br>
><br>
> ><br>
><br>
> > "testing git-cvsserver" proses "Clean cut" with the additional ability<br>
><br>
> > to continue using cvs update/commit, - in best case - on the old<br>
><br>
> > checkout w/o alteration on the developers side.<br>
><br>
> ><br>
><br>
> > "Clean cut" forces us to clean up out dirty checkouts (I have some<br>
><br>
> > added directories, added ebuilds i hesitated to `repoman commit`).<br>
><br>
> > Plus we have to alter all our hot-wired portage mangling scripts from<br>
><br>
> > cvs'ish to git'ish (I use my read/write checkout as portage tree (cvs<br>
><br>
> > checkout + egencache for checkout) and have an automated google-chrome<br>
><br>
> > bump script). But this can be accomplished on a per developer basis,<br>
><br>
> > and slackers don't stall the process.<br>
><br>
> ><br>
><br>
> > "testing git-cvsserver" forces us all to test these cvs'ish scripts<br>
><br>
> > and behaviours against a git-cvsserver and report.<br>
><br>
> > We all know that this test-runs will never happen, stalling this bug<br>
><br>
> > till infinity.<br>
><br>
> > Plus infra/"subset of devs marshalling the migration" get stuck<br>
><br>
> > between fixing git issues and git-cvsserver.<br>
><br>
> ><br>
><br>
> > *if you still read this* *wow*<br>
><br>
> ><br>
><br>
> > Please discuss my arguments and come to the conclusions to<br>
><br>
> > RESO/WONT-FIX "testing git-cvsserver", make a "clean cut" and remove<br>
><br>
> > this bug from the blockers of "[TRACKER] portage migration to git".<br>
><br>
> ><br>
><br>
> > My lengthy 2 cents.<br>
><br>
> ><br>
><br>
> > [1] <a href="https://bugs.gentoo.org/333531">https://bugs.gentoo.org/333531</a><br>
><br>
> > [2] <a href="https://bugs.gentoo.org/333699">https://bugs.gentoo.org/333699</a><br>
><br>
> > [3] <a href="https://bugs.gentoo.org/333705#c2">https://bugs.gentoo.org/333705#c2</a><br>
><br>
> > - --<br>
><br>
> > Gentoo Dev<br>
><br>
> > <a href="http://xmw.de/">http://xmw.de/</a><br>
><br>
> > -----BEGIN PGP SIGNATURE-----<br>
><br>
> > Version: GnuPG v2.0.17 (GNU/Linux)<br>
><br>
> > Comment: Using GnuPG with Mozilla - <a href="http://enigmail.mozdev.org/">http://enigmail.mozdev.org/</a><br>
><br>
> ><br>
><br>
> > iF4EAREIAAYFAk+82z0ACgkQknrdDGLu8JBUWAD/dmuqyES/mYDrMam+/txnHmgd<br>
><br>
> > VaQaqwHMlwzzqQwbpY4A/0h+5Vp8sLbOE78k4SCaGE2dCQtmeOz0jd1YxkDzP+YW<br>
><br>
> > =jXLQ<br>
><br>
> > -----END PGP SIGNATURE-----<br>
><br>
> <br>
><br>
> I support RESOLUTION WONTFIX, if nobody cares about the bug since it was opened it is obvious out of interest. There is no reason to support jurassic software.<br>
><br>
> <br>
><br>
> Clean cut++<br>
><br>
> <br>
><br>
> Cheers<br>
><br>
> --<br>
><br>
> Johannes Huber (johu)<br>
><br>
> Gentoo Linux Developer / KDE Team<br>
><br>
> GPG Key ID F3CFD2BD<br>
><br>
> </p>
<p>Another vote for clean cut from me.</p>
|
|
