From: Jan Dubiec <jdx@slackware.pl>
To: Cory Visi <merlin@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Patches for MPPE/MPPC
Date: 29 Aug 2004 13:02:09 +0200 [thread overview]
Message-ID: <87brgu5hse.fsf@hs001.slackware.pl> (raw)
In-Reply-To: <20040825172450.GB20213@toucan.gentoo.org>
On Wed, 25 Aug 2004 17:24:50 +0000, Cory Visi <merlin@gentoo.org> wrote:
> Hi all. I am working on some ppp bugs and I noticed there is an excellent
> kernel patch for MPPE/MPPC available for both 2.4 and 2.6 kernel versions:
Thanks ;-)
[.....]
> 1. Can I include the ppp patch in the ppp ebuild? How do I do it legally?
IMO the *pppd* patch can be included because it doesn't contain actual MPPC
code. MPPC (de)compresion routines are located in the *kernel* patch.
> 2. Can we include the kernel patch in the gentoo-sources base patch set?
> How do we do it legally?
IMO, if Gentoo servers are outside the USA (e.g. in the EU), the patches
could be included. Although I am not a lawyer.
I have one question - does somebody of you know if my patches are included
in an unofficial Gentoo sources? I am asking because I am receiving a lot
of emails from people who use Gentoo and my patches. They use "stdopt"
(e.g. ppp-2.4.2-stdopt-mppe-mppc-1.1.patch.gz) version of the pppd patch.
It has MPPE/MPPC related options compatible with original pppd-2.4.2.
Unfortunately, because of that it inherits also a few drawbacks of the
original. So if you decide to include my patches into Gentoo sources, I
recommend using non-"stdopt" pppd patch (i.e. ppp-2.4.2-mppe-mppc-1.1.patch.gz).
I generates much less email traffic from unexperienced users.
Regards,
/J.D.
--
Jan Dubiec, jdx#slackware.pl, mobile: +48 506 790442
Głęboka wiara wymaga płytkiego rozumu i nikłej wiedzy.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-08-29 11:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 17:24 [gentoo-dev] Patches for MPPE/MPPC Cory Visi
2004-08-25 17:40 ` Mike Frysinger
2004-08-29 8:25 ` John Huttley
2004-08-29 11:43 ` Jan Dubiec
2004-08-29 11:02 ` Jan Dubiec [this message]
2004-08-30 4:09 ` Cory Visi
2004-08-30 17:27 ` Jan Dubiec
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=87brgu5hse.fsf@hs001.slackware.pl \
--to=jdx@slackware.pl \
--cc=gentoo-dev@lists.gentoo.org \
--cc=merlin@gentoo.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