[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev dead code & 2-8-2
From: |
Philip Webb |
Subject: |
Re: lynx-dev dead code & 2-8-2 |
Date: |
Sun, 14 Mar 1999 23:40:33 -0500 (EST) |
990314 John Bley wrote:
> On Sun, 14 Mar 1999, Philip Webb wrote:
>> one of my suggestions in response to JB's request for comments was
>> to hold his clean-up till immediately after 2-8-2rel.1 ,
>> then make them the defining patches for 2-8-3dev.1 .
> I can't promise I'll have time to work on lynx
> at any given point in future: I have free time now,
> but in a few weeks it'll be final-exam-project-paper crunch time,
> then I go somewhere to work during the summer,
> then I start grad school. Yikes!
been there, done that ... (grin).
> I've submitted patches/rationales for what I consider
> the most flagrant chunks of dead code, like whole files.
> The dead code can be chopped at any point that's convenient.
> If y'all are more comfortable doing that at the start of a new dev-cycle,
> then that's the way it should be done.
i'ld say -- subject to correction by others in the consensus --
that you should create a set of patches now -- while you have time --
based on 2-8-2dev.19 , which is likely to be close enough to 2-8-2rel.1 ,
& submit them straight away, marked clearly `dead-code patch (1)' etc;
try to chop them into sensible bite-size pieces (as you've already done).
they will stay in the Archive anyway & i will certainly create
my own ~/Mail/lynx/lynx-deadbits/ subdirectory to store them all,
given that TD is seriously overworked & a bit distracted at the moment.
then once 2-8-2rel.1 is out, we can decide how to use them,
with your own input if you're available at that time.
if your patches don't match the ultimate 2-8-2rel.1 exactly,
that's a detail we can sort out at the time.
but NBB: they must be PATCHES, not rationales or lists of functions etc:
in real lynx-dev life, no-one else will put in the labor
to convert them from the latter to the former:
your work will have been wasted & by the time you get back to it
Lynx development will have moved on & the convenient opportunity been lost.
and do include ALL you think can be dropped:
we can decide not to use some of it, if that's the consensus.
--
========================,,============================================
SUPPORT ___________//___, Philip Webb : address@hidden
ELECTRIC /] [] [] [] [] []| Centre for Urban & Community Studies
TRANSIT `-O----------O---' University of Toronto