From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] pppd: bugfixes and enhancements
Date: Fri, 21 Oct 2011 07:37:58 -0300 [thread overview]
Message-ID: <f01ca2a6c070eb9cdede59ea0a984da1@zacarias.com.ar> (raw)
In-Reply-To: <20111021085121.13ff68d3@skate>
On 21.10.2011 03:51, Thomas Petazzoni wrote:
> Have those patches been submitted upstream ? We really don't want to
> start accumulating too many non-build related patches, such as bug
> fixes or feature additions.
>
> Thanks!
>
> Thomas
Yes.
Debian and OpenWRT have some of them too (not quite exactly the same
but they do the same).
It's pretty likely that the default gateway patch won't be merged
upstream from what i've read, the argument being somewhat in the lines
of desktop security versus embedded and siding with the first. However
it's pretty much required for openswan to work correctly or we'd have to
do some very nasty scripts to deal with it (openswan not working out of
the box).
Regards.
prev parent reply other threads:[~2011-10-21 10:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-20 17:48 [Buildroot] [PATCH 1/4] pppd: bugfixes and enhancements Gustavo Zacarias
2011-10-20 17:48 ` [Buildroot] [PATCH 2/4] ocf: new package Gustavo Zacarias
2011-10-21 6:53 ` Thomas Petazzoni
2011-10-21 10:33 ` Gustavo Zacarias
2011-10-21 10:56 ` Thomas Petazzoni
2011-10-20 17:48 ` [Buildroot] [PATCH 3/4] openssl: split out ocf Gustavo Zacarias
2011-10-20 17:48 ` [Buildroot] [PATCH 4/4] openswan: new package Gustavo Zacarias
2011-10-21 6:51 ` [Buildroot] [PATCH 1/4] pppd: bugfixes and enhancements Thomas Petazzoni
2011-10-21 10:37 ` Gustavo Zacarias [this message]
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=f01ca2a6c070eb9cdede59ea0a984da1@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--cc=buildroot@busybox.net \
/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