On Mon, May 16, 2011 at 07:41, Mark Loeser <halcy0n@gentoo.org> wrote:
> "Mike Frysinger (vapier)" <vapier@gentoo.org> said:
>> vapier * * *11/05/16 03:30:02
>>
>> * Removed: * * * * * * *bzip2-1.0.5-r1.ebuild
>> * Log:
>> * old
>
> Please document removal of ebuilds in ChangeLogs.

It would also seem manifests weren't regenerated. Don't have the time
to go look if they were all touched by the same individual, but since
Friday afternoon bzip2, cabextract, rsyslog, rubygems, and
ca-certificates all come up with files missing from the manifest.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

W dniu 16.05.2011 15:41, Mark Loeser pisze:
> "Mike Frysinger (vapier)" <vapier@gentoo.org> said:
>> vapier 11/05/16 03:30:02
>>
>> Removed: bzip2-1.0.5-r1.ebuild
>> Log:
>> old
>
> Please document removal of ebuilds in ChangeLogs.
>
> http://devmanual.gentoo.org/ebuild-writing/misc-files/changelog/
>
> It'd also be better to do this all as one commit and run repoman with
> each commit.
>
> Thanks,
I don't understand the purpose of such mails (it's 2nd within the
period of few days).
Council have already voted that those changes should be added to
changelog so there's nothing technical to discuss.

As for the conflict resolution the policy states:
1) try to resolve the issue among yourselves
2) consult with the project lead (QA?)
3) if all fails go to devrel
Neither of those points include sending mail to gentoo-dev, which tend
to quickly convert into the "witch hunt" and seldom lead to anything
conclusive.
Cheers,
Kacper
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iJwEAQECAAYFAk3RZMwACgkQIiMqcbOVdxRGuAP+JHinAeoeYq SxAqfjqcP5Q922
Jr8E4IPPpazlVUeWrtg2uHOIShkHQI8l5djiJ7mnsVGkRooPib X4ndX9rHLkwErH
XahKTnHiUPSl1qoMr6f5fyqjQQ7O6dvpVXpT9O6g1/lyRmbnTB2dj6ts5trO88XL
n7ehyPhupEewFjGAjbU=
=Lvvm
-----END PGP SIGNATURE-----

El 16/05/11 19:54, Kacper Kowalik escribió:
> Neither of those points include sending mail to gentoo-dev, which tend
> to quickly convert into the "witch hunt" and seldom lead to anything
> conclusive.
To some of us (i.e. me as a staffer and probably any wanna be developer
following the list) it is a good way to learn from others' mistake
before applying for full developership.

On Mon, May 16, 2011 at 08:19:45PM +0200, Francisco Blas Izquierdo Riera (klondike) wrote:
> El 16/05/11 19:54, Kacper Kowalik escribió:
> > Neither of those points include sending mail to gentoo-dev, which tend
> > to quickly convert into the "witch hunt" and seldom lead to anything
> > conclusive.
> To some of us (i.e. me as a staffer and probably any wanna be developer
> following the list) it is a good way to learn from others' mistake
> before applying for full developership.
>

This may be a bit of surprise to you but this is not an educational
list. If you people disagree with these kind of commits feel free to
open a bug to QA/Devrel like the policy suggests. But pretty please
try to break this non-sense loop of this and similar threads.

Regards,
--
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2