From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] openvpn: adjust iproute2 logic
Date: Thu, 04 Apr 2013 18:33:32 -0300 [thread overview]
Message-ID: <515DF1AC.8060506@zacarias.com.ar> (raw)
In-Reply-To: <878v4y3tp2.fsf@dell.be.48ers.dk>
On 04/04/2013 05:51 PM, Peter Korsgaard wrote:
> We'll most likely forget to update this next time we bump the busybox
> version, and not notice it as it's a runtime issue.
>
> Could you invert the logic so you explicitly check for the old busybox
> versions instead?
True.
We'll likely forget to remove dead code too later on, but it doesn't hurt :)
Regards.
next prev parent reply other threads:[~2013-04-04 21:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-04 16:54 [Buildroot] [PATCH] openvpn: adjust iproute2 logic Gustavo Zacarias
2013-04-04 20:51 ` Peter Korsgaard
2013-04-04 21:33 ` Gustavo Zacarias [this message]
2013-04-07 7:43 ` Peter Korsgaard
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=515DF1AC.8060506@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