A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2000-February/001982.html below:

[Python-Dev] patch handling (was: Python 1.6 timing)

[Python-Dev] patch handling (was: Python 1.6 timing) [Python-Dev] patch handling (was: Python 1.6 timing)David Ascher da@ski.org
Wed, 2 Feb 2000 17:04:46 -0800
From: "Guido van Rossum" <guido@CNRI.Reston.VA.US>
To: <python-dev@python.org>
Sent: Wednesday, February 02, 2000 4:50 PM
Subject: Re: [Python-Dev] patch handling (was: Python 1.6 timing)


> > I assume you'll get a similar response from many people: hopefully,
> > for each patch it will either get booed automatically (hey! I just added
> > braces instead of indentation to the parser) or will interest someone.
>
> The thing here that makes me slightly uncomfortable is how to keep
> track of patches that nobody picks up.

Sourceforge has a nice patch manager which allows a GUI'ish view of patches
in context, discarding/deferring/etc.  The code is available and open
source.

--david




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