--boogadaboogadabooga Content-Type: text/plain; charset="us-ascii" Folks, I posted this message to the patches mailing list last week, but either I missed the reply (we had full disks over the weekend) or nobody replied yet. And I am waiting for these patches, or rather other people who want to play with MacPython and MacOSX are, so I'd really like to know whether I should revise the patches and in what direction or have them checked in.... Hmm, that may all sound a bit pushy, but that isn't the intention. I really just want to know (a) what the status of my patches is and (b) what I can expect in the future.... Jack --boogadaboogadabooga Content-Type: message/rfc822 From jack@oratrix.nl Sat Jun 3 13: 06:03 2000 Delivered-To: jack@oratrix.nl Received: by oratrix.oratrix.nl (Postfix, from userid 201) id 63987D7210; Sat, 3 Jun 2000 13:06:02 +0200 (MET DST) Received: from localhost (localhost [127.0.0.1]) by oratrix.oratrix.nl (Postfix) with ESMTP id 3EED619B1E9A; Sat, 3 Jun 2000 13:05:57 +0200 (MET DST) To: patches@python.org Cc: jack@oratrix.nl Subject: Re: [Patches] Patch to import.c In-Reply-To: Message by Greg Stein <gstein@lyra.org> , Sat, 3 Jun 2000 03:26:25 -0700 (PDT) , <Pine.LNX.4.10.1000 6030325330.29036-100000@nebula.lyra.org> Organisation: Oratrix Development, Valeriusplein 30, 1075 BJ Amsterdam, NL Phone: +31 20 6795452(work), +31 20 6795309 (fax), +31 20 6160335(home) X-Last-Band-Seen: Stiff Little Fingers (Melkweg, 4-5) X-Mini-Review: Absolutely brilliant!!! Date: Sat, 03 Jun 2000 13:05:57 +0200 From: Jack Jansen <jack@oratrix.nl> Return-Path: <jack@oratrix.nl> Message-Id: <20000603110602.63987D7210@oratrix.oratrix.nl> I'm a bit confused as to the current procedure for patches. It used to be that Guido said "yes" or "no", and that was it. Nowadays there seem to be very many people on the patches mailing list, and a patch gets a number of replies ranging from "don't do this" to "can't you do this differently". I've tried to reply to all the issues, but I'm now completely in the dark as to the status of my patches: I'm under the impression that I've defended the case for my patches satisfactorily (hehe:-), but people on the patch mailing list may think that I've some fixing up to do. As I didn't follow discussions on the new patch system: is there a procedure and, if so, could it be documented on python.org/patches? And if there isn't one: could one be designed and documented, please? A time-limit on patch acceptance/rejection would also be nice, if possible: I use the repository to sync my home machine and work machine, which worked fine when Guido alone was responsible as he worked what seems to be 19 hours per day, so patches usually ended up in the repository before I had the chance to cycle from home to work or vv., but with the new procedure it can apparently take a lot longer for patches to appear, so I may have to come up with another scheme to sync my multiple machines... -- Jack Jansen | ++++ stop the execution of Mumia Abu-Jamal ++++ Jack.Jansen@oratrix.com | ++++ if you agree copy these lines to your sig ++++ www.oratrix.nl/~jack | see http://www.xs4all.nl/~tank/spg-l/sigaction.htm --boogadaboogadabooga--
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4