From: Jonatan Schlag <jonatan.schlag@ipfire.org>
To: network@lists.ipfire.org
Subject: Split the cmd line parsing in the config hooks in seperated functions
Date: Wed, 19 Jul 2017 10:52:34 +0200 [thread overview]
Message-ID: <1500454358-6561-1-git-send-email-jonatan.schlag@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 222 bytes --]
Hi the following patches just do what is stated in the subject.
If anything else could be improved (I know some code which is touched here and could be improved) i would like to do this when this patchset is merged.
next reply other threads:[~2017-07-19 8:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 8:52 Jonatan Schlag [this message]
2017-07-19 8:52 ` [PATCH 1/4] pppoe-server: create hook_parse_cmdline function Jonatan Schlag
2017-07-19 8:52 ` [PATCH 2/4] ipv6-static: " Jonatan Schlag
2017-07-19 8:52 ` [PATCH 3/4] ipv6-auto: " Jonatan Schlag
2017-07-19 8:52 ` [PATCH 4/4] ipv4-static: " Jonatan Schlag
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=1500454358-6561-1-git-send-email-jonatan.schlag@ipfire.org \
--to=jonatan.schlag@ipfire.org \
--cc=network@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