From: Jonatan Schlag <jonatan.schlag@ipfire.org>
To: network@lists.ipfire.org
Subject: [PATCH 5/8] header-config: add generic hhok_hid function
Date: Tue, 25 Jul 2017 18:07:10 +0200 [thread overview]
Message-ID: <1500998833-10543-6-git-send-email-jonatan.schlag@ipfire.org> (raw)
In-Reply-To: <1500998833-10543-1-git-send-email-jonatan.schlag@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 673 bytes --]
This function will always be there so when we call hhok_hid we will get a result.
This is also nice for testing.
Signed-off-by: Jonatan Schlag <jonatan.schlag(a)ipfire.org>
---
| 8 ++++++++
1 file changed, 8 insertions(+)
--git a/src/header-config b/src/header-config
index e3c6423..76f4bb5 100644
--- a/src/header-config
+++ b/src/header-config
@@ -76,3 +76,11 @@ hook_edit() {
exit ${EXIT_OK}
}
+
+# We will return the id as generic variant of the hid
+# Although this should not be the standard
+hook_hid() {
+ assert [ $# -eq 1 ]
+ local config=${1}
+ echo $(config_get_id_from_config ${config})
+}
--
2.6.3
next prev parent reply other threads:[~2017-07-25 16:07 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-25 16:07 Add hids Jonatan Schlag
2017-07-25 16:07 ` [PATCH 1/8] zone: add config hid functions Jonatan Schlag
2017-07-25 22:22 ` Michael Tremer
2017-07-25 16:07 ` [PATCH 2/8] zone: accept also hids in zone_config() Jonatan Schlag
2017-07-25 22:27 ` Michael Tremer
2017-07-25 16:07 ` [PATCH 3/8] zone: config list print also hids Jonatan Schlag
2017-07-25 22:28 ` Michael Tremer
2017-07-25 16:07 ` [PATCH 4/8] hook: also hook_hid is a valid command Jonatan Schlag
2017-07-25 16:07 ` Jonatan Schlag [this message]
2017-07-25 22:29 ` [PATCH 5/8] header-config: add generic hhok_hid function Michael Tremer
2017-07-25 16:07 ` [PATCH 6/8] raw: add command list-zone-config-hids Jonatan Schlag
2017-07-25 16:07 ` [PATCH 7/8] raw: add command zone-config-hid-is-valid Jonatan Schlag
2017-07-25 16:07 ` [PATCH 8/8] autocompletion: use hids instead of ids Jonatan Schlag
2017-07-25 22:30 ` Michael Tremer
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=1500998833-10543-6-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