From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] package: dropbear: add support for displaying /etc/motd
Date: Thu, 23 May 2019 15:18:05 +0200 [thread overview]
Message-ID: <87k1ehs41e.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20190523142857.625748aa@windsurf.home> (Thomas Petazzoni's message of "Thu, 23 May 2019 14:28:57 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
Hi,
> This way, we have something that is much more flexible, as it allows
> you to define whatever Dropbear option you like.
> Note: this is just a suggestion; I don't know what other
> maintainers/developers will think about it.
Agreed, if we want such finegrained configuration then that would be the
way to go.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2019-05-23 13:18 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 12:11 [Buildroot] [PATCH] package: dropbear: add support for displaying /etc/motd Alexandru Ardelean
2019-05-23 12:28 ` Thomas Petazzoni
2019-05-23 13:00 ` Alexandru Ardelean
2019-05-23 13:18 ` Peter Korsgaard [this message]
2019-05-24 7:50 ` Peter Korsgaard
2019-05-29 6:51 ` Alexandru Ardelean
2019-05-29 10:27 ` [Buildroot] [PATCH] dropbear: add build opt to provide file with localoptions.h Alexandru Ardelean
2019-06-01 10:36 ` Thomas Petazzoni
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=87k1ehs41e.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--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