Victor Stinner victor.stin...@haypocalc.com writes:
Le lundi 14 mars 2011 à 15:36 -0400, David Bolen a écrit :
Speaking of bbreport, I sometimes use the published page on that site
(http://code.google.com/p/bbreport/wiki/PythonBuildbotReport) to check
over things, but looking at it today, it
Le lundi 14 mars 2011 à 15:36 -0400, David Bolen a écrit :
Antoine Pitrou solip...@pitrou.net writes:
I suggest you try http://code.google.com/p/bbreport/, which provides a
very nice command-line interface.
Speaking of bbreport, I sometimes use the published page on that site
Traditionally I could see who was the committer who push change to the
buildbots. This info seems not to be (easily) available.
I have now restored that information in the buildbot. However, only
includes the committer, not the pusher. Traditionally, they were the
same thing, but they are not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 15/03/11 21:14, Martin v. Löwis wrote:
Traditionally I could see who was the committer who push change to the
buildbots. This info seems not to be (easily) available.
I have now restored that information in the buildbot. However, only
On Mon, 14 Mar 2011 17:59:27 +0100
Jesus Cea j...@jcea.es wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Traditionally I could see who was the committer who push change to the
buildbots. This info seems not to be (easily) available.
That info was lost quite before the hg migration,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 14/03/11 18:07, Antoine Pitrou wrote:
On Mon, 14 Mar 2011 17:59:27 +0100
Jesus Cea j...@jcea.es wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Traditionally I could see who was the committer who push change to the
buildbots. This
Antoine Pitrou solip...@pitrou.net writes:
I suggest you try http://code.google.com/p/bbreport/, which provides a
very nice command-line interface.
Speaking of bbreport, I sometimes use the published page on that site
(http://code.google.com/p/bbreport/wiki/PythonBuildbotReport) to check
over
