From: Ralf Baechle DO1GRB <ralf@uni-koblenz.de>
To: Iain Young - G7III <g7iii@g7iii.demon.co.uk>
Cc: linux-hams@vger.kernel.org
Subject: Re: KJD 2.3.9 patch on 2.5.29
Date: Mon, 5 Aug 2002 20:16:01 +0200 [thread overview]
Message-ID: <20020805201601.A25963@dea.linux-mips.net> (raw)
In-Reply-To: <20020805171956.GA566@columbia.g7iii.bogus>; from g7iii@g7iii.demon.co.uk on Mon, Aug 05, 2002 at 06:19:56PM +0100
On Mon, Aug 05, 2002 at 06:19:56PM +0100, Iain Young - G7III wrote:
> > I'll make them available asap; I've still a huge number of loose ends to
> > solve, hours of typing ahead ...
>
> Heh, I know that feeling :)
I've fixed many of them now and I'm just trying to setup a repository
on bkbits.net but keep running into problem
> > Thanks for reminding me of that code again. I'd not mind taking that
> > patch as a base to start with. However the author doesn't even claim it
> > to be working and the patch only minimally deals with the problems that
> > the current code is suffering from. I also had a conversation with
> > Alan Cox (GW4PTS) who originally wrote the code. Alan wasn't fond at all
> > of newax25 because the oldcode despite it's problem is fairly stable in
> > practical use. So I came to the conclusion the the best thing will be if
> > I first solve the problems of the current codebase and then later import
> > code from the DG1KJD.
>
> Yeah, that is actually a good point from Alan. And there are things that
> KJD code does that I consider 'wrong' - see my previous recent emails on
> 'network purity'.
>
> I believe it also changes the interface definitions, and needs a modified
> libax25/apps/tools.
Yuck.
> For what its worth, I did get quite far in getting it merged into a
> 2.5.29 tree. Got approximatley 50% of the rejects sorted, but most of
> the remaining ones were the soundmodem, and scc drivers.
>
> Unfortunatley, most of the remainder are in the core AX25 code, and
> one reject in particular is 60K!
I've merged the DG1KJD code into 2.4-latest without major problems. The
bitkeeper tools have helped me alot making that easier.
73 de DO1GRB op Ralf
--
Loc. JN47BS / CQ 14 / ITU 28 / DOK A21
next prev parent reply other threads:[~2002-08-05 18:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-01 19:46 KJD 2.3.9 patch on 2.5.29 Iain Young - G7III
2002-08-01 21:33 ` Hans-Peter Zorn
2002-08-02 18:38 ` Iain Young - G7III
2002-08-02 0:32 ` Ralf Baechle DO1GRB
2002-08-02 18:28 ` Iain Young - G7III
2002-08-05 12:28 ` Ralf Baechle DO1GRB
2002-08-05 17:19 ` Iain Young - G7III
2002-08-05 18:16 ` Ralf Baechle DO1GRB [this message]
2002-08-05 19:16 ` Ralf Baechle DO1GRB
2002-09-12 17:41 ` Joaquin Seoane
2002-10-01 11:39 ` KJD 2.3.9 patch on 2.5.29 (NOT FOUND) Joaquin Seoane
2002-08-05 18:02 ` KJD 2.3.9 patch on 2.5.29 Ray Heasman
2002-08-05 19:11 ` Ralf Baechle DO1GRB
2002-08-05 19:35 ` M Taylor
2002-08-06 10:22 ` Ralf Baechle DO1GRB
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020805201601.A25963@dea.linux-mips.net \
--to=ralf@uni-koblenz.de \
--cc=g7iii@g7iii.demon.co.uk \
--cc=linux-hams@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox