From: William Hubbs <williamh@gentoo.org>
To: gentoo development <gentoo-dev@lists.gentoo.org>
Subject: Re: [gentoo-dev] rfc: *_iface variables in openrc network scripts
Date: Wed, 11 May 2011 20:55:28 -0500 [thread overview]
Message-ID: <20110512015528.GA29093@linux1> (raw)
In-Reply-To: <20110512014540.GA28033@linux1>
[-- Attachment #1: Type: text/plain, Size: 487 bytes --]
Yeah I know I'm replying to my own message, but I also have another idea
about this. Another option would be that for the next release we just
stop parsing and use config_* but without trying to do any conversions.
The disadvantage of this would be that people would have to change their
/etc/conf.d/net files immediately after they upgrade or their network
might not come up.
It is true that this would be easier from a coding perspective, but
would it be ok for the users?
William
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-05-12 1:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-12 1:45 [gentoo-dev] rfc: *_iface variables in openrc network scripts William Hubbs
2011-05-12 1:55 ` William Hubbs [this message]
2011-05-12 9:35 ` Petteri Räty
2011-05-12 2:01 ` Jorge Manuel B. S. Vicetto
2011-05-12 14:34 ` William Hubbs
2011-05-12 23:49 ` Jorge Manuel B. S. Vicetto
2011-05-13 2:18 ` William Hubbs
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=20110512015528.GA29093@linux1 \
--to=williamh@gentoo.org \
--cc=gentoo-dev@lists.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