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-June/004938.html below:

[Patches] Let's use the SourceForge Patch Manager

[Python-Dev] Re: [Patches] Let's use the SourceForge Patch Manager [Python-Dev] Re: [Patches] Let's use the SourceForge Patch ManagerKa-Ping Yee Ka-Ping Yee <pingster@ilm.com>
Tue, 27 Jun 2000 16:29:04 -0700 (PDT)
Fredrik Lundh wrote:
> someone really needs to fuse the patch manager with roundup (that
> we should use roundup for bug tracking goes without saying...)

How sweet!  Why, thank you. :)

Trent Mick wrote:
> What are the chances of getting other meta data fields on patches, i.e.
> changes to the patch manager? Categorizing patches could really help as a
> filter. For instance, I may be a Unicode genius and would like to see the
> patches associated with it.

I agree that doing that kind of filtering is very useful.  I have
a discussion thingie (based on Roundup) at http://headspaces.com/.
(Also prototype -- very prototype.)  I hacked out the "status" and
"fixer" fields and added a "keywords" field.  Not much volume yet,
but i think it will work well.

Perhaps something like that for discussing patches?

Jeremy Hylton wrote:
> Maybe the right solution is to work with the SourceForge maintainers
> to make roundup part of the standard support software.  

Hmmm... maybe i should look into that after i've figured out how
super-Roundup is going to work.


-- ?!ng





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