From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: work in progress: ppp 2.4.9
Date: Thu, 01 Apr 2021 10:35:42 +0100 [thread overview]
Message-ID: <A5EE81B2-6C3E-43B6-A1FA-5355610B5222@ipfire.org> (raw)
In-Reply-To: <d6009f83-e9f0-9792-e49b-b9b8372461a8@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 782 bytes --]
Hello,
It seems that a new maintainer has taken over pppd and started with merging many upstream patches that various distributions have been carrying around with them for a long time.
All patches currently in next are security stuff and no functionality. It might not be bad if this patch does not apply exactly if the new maintainer(s) found a different solution.
I believe some of the patches are rather hacky.
Best,
-Michael
> On 31 Mar 2021, at 18:01, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>
> Hello development folks,
>
> for your information: I am currently working on ppp 2.4.9, which turns out to be rather
> tricky as many of our patches won't apply and/or are not necessary anymore.
>
> Thanks, and best regards,
> Peter Müller
next parent reply other threads:[~2021-04-01 9:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d6009f83-e9f0-9792-e49b-b9b8372461a8@ipfire.org>
2021-04-01 9:35 ` Michael Tremer [this message]
2021-04-01 16:34 ` Peter Müller
2021-04-01 16:41 ` Michael Tremer
2021-04-01 16:53 ` Peter Müller
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=A5EE81B2-6C3E-43B6-A1FA-5355610B5222@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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