[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LYNX-DEV Lynx 3.0
Nelson Henry Eric
Re: LYNX-DEV Lynx 3.0
Fri, 28 Feb 1997 10:16:31 +0900 (JST)
> First, my changes documentation are slim. It is currently contained in
> that little 386-WIN.TXT file.
It's a start. Important I would say is that whatever documentation there
is, it should be zipped right into the distribution. I would rcommend that
a common name be chosen for a file that each contributor can add to, rather
than having a specific name for each particular mod. In other words, just
change the name of 386-WIN.TXT to CHANGES (or some other name of your choice),
hopefully dating and signing it. The next developer could then just add
whatever he or she has (Klaus? Rob? Hiram?).
> We have three main codesets coming:
> Lynx2.7 + FM fixes + Wayne's mods
> Lynx2.7 + FM fixes + Klaus's mods + Hiram's mods
> Lynx2.7 + Rob's mods + Hiram's mods + FM fixes (?)
> I am thinking that maybe I should pull back since my code is easy to
I'd hate to see you do that, but it is ultimately your choice. I cannot
understand why we can't have a first-come-first-serve system, so that
the above is not three code sets, but ONE continuum:
((((Lynx2.7+FM fixes+Wayne's mods)+Klaus's mods)+Hiram's mods)+Rob's mods)
As far as I know, the underlined portion in fact exists; it's just a matter
of replacing and/or patching a few files, and then zipping it all together
with a unique name (and hopefully with documentation). Documentation can
always be added in later as diff -c patches. Bug fixes would be posted
against the "then active snapshot" (thus a need for a date or some specific
identifier, and the need for a record of changes). Fote's continuing bug
fixes for Lynx2.7 could be pasted in by hand if need be.
> I am just getting nervous because of the size of the mods from Klaus and
> Rob. Maybe they feel like I do in that they can overlay their stuff over
> anything because they know it well...
You of course can, but we (at least I) can't. That's pretty much what
happened to Klaus's work on WWWlib as I see it. It never got incorporated,
so it never had a chance to be tested, so it got forgotten for the large part.
I'm sorry, but all I can offer to do is exercise what's there. You developers
will have to work as a team without a captain. I hope you all will be able
to find a system that works for you. As long as there is a consensus, there
is no reason the distribution site (downloading site) couldn't create the
product. Just take the steer by the horns and go for it.
; To UNSUBSCRIBE: Send a mail message to address@hidden
; with "unsubscribe lynx-dev" (without the
; quotation marks) on a line by itself.
Re: LYNX-DEV Lynx 3.0, Matt Ackeret, 1997/02/27
Re: LYNX-DEV Lynx 3.0, Nelson Henry Eric, 1997/02/27
Re: LYNX-DEV Lynx 3.0,
Nelson Henry Eric <=
Re: LYNX-DEV Lynx 3.0, David Combs, 1997/02/27