--===============1385469364==
Content-Type: multipart/signed;
  boundary="nextPart8069137.Dm7dB68PtG";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart8069137.Dm7dB68PtG
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Em Sexta-feira 13 Novembro 2009, =E0s 15:28:35, voc=EA escreveu:
> As for the actual topic of the thread; aren't you trying to find a
> cure for a symptom here? Even if you knew exactly who committed it,
> the code would still be bad and/or evil. So either the ring of people
> you trust with commit access is too big or you don't have enough peer
> reviews as I see it. Not that I'm against the idea of implementing
> some kind of tracking here, it just seems like the wrong place to try
> and fix things to me. But then again, I'm not really part of the KDE
> community so my point is probably moot here..
>=20

Basically what we need is a push log.

Since we need that for Qt too, I've been thinking of writing the hook anywa=
y.

=2D-=20
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

--nextPart8069137.Dm7dB68PtG
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iD8DBQBK/W+RM/XwBW70U1gRAipRAKCh45ZHA/cPutaqyXkkWW8Wso0wwACZAd3k
P3+dlaaqRjJOgMd2MNRKkv8=
=iBsd
-----END PGP SIGNATURE-----

--nextPart8069137.Dm7dB68PtG--

--===============1385469364==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest

--===============1385469364==--