> As far as I'm concerned, +1 for Gerhard being able to checkin vc6 related
> makefiles to the trunk without review (notwithstanding any other
> restrictions imposed by the release manager, etc.)
Hmm - it might be easier to just review them. What's the patch number again?
Regards,
Martin
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 22, 2008, at 4:02 AM, Mark Hammond wrote:
sorry if you were aware of that already, but VC6 isn't the compiler
for
the official builds. The VC6 files are "only" alternative
"Makefiles".
As far as I'm concerned, +1 for Gerhard being able t
> sorry if you were aware of that already, but VC6 isn't the compiler for
> the official builds. The VC6 files are "only" alternative "Makefiles".
As far as I'm concerned, +1 for Gerhard being able to checkin vc6 related
makefiles to the trunk without review (notwithstanding any other
restrictions
Barry Warsaw wrote:
On Sep 19, 2008, at 8:06 AM, Hirokazu Yamamoto wrote:
Hello. Can I commit VC6 related patch without review?
I want to bump up external library versions (bsddb, sqlite3 etc) to
follow
PCBuild.
Since we're in release candidate, please have one of the Windows experts
revie
> Since we're in release candidate, please have one of the Windows
> experts review your changes. If this is a blocker issue for the final
> release, open a bug and set the priority to 'release blocker' and
> attach your diff to the issue.
>
> Thanks,
> - -Barry
OK, Thanks.
___
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 19, 2008, at 8:06 AM, Hirokazu Yamamoto wrote:
Hello. Can I commit VC6 related patch without review?
I want to bump up external library versions (bsddb, sqlite3 etc) to
follow
PCBuild.
Since we're in release candidate, please have one of
Hello. Can I commit VC6 related patch without review?
I want to bump up external library versions (bsddb, sqlite3 etc) to follow
PCBuild.
Thank you.
___
python-committers mailing list
python-committers@python.org
http://mail.python.org/mailman/listinfo/
