From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] docs/website: add commercial support section with Mind
Date: Mon, 27 Jan 2020 17:49:34 +0100 [thread overview]
Message-ID: <875zgwsv35.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20200126154245.GQ32369@scaer> (Yann E. MORIN's message of "Sun, 26 Jan 2020 16:42:45 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> Arnout, All,
> On 2020-01-24 11:37 +0100, Arnout Vandecappelle (Essensium/Mind) spake thusly:
>> Add a section to the support page for commercial support.
>>
>> Add a box for Mind in that section.
>>
>> This can be used as an example for other companies that provide
>> technical support for Buildroot.
>>
>> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
>> ---
>> There has been some discussion (off-list) about how to formalize
>> acceptance criteria for companies to be added to this commercial support
>> section, but without conclusion AFAIU. So I thought I'd go ahead and
>> just add one example that should be uncontroversial :-)
>>
>> I have not looked at how it looks in the browser, because I don't know
>> how to deploy the website in a way that I can preview it...
> $ git clone https://github.com/danvk/ssi-server.git ~/tmp/ssi-server
> $ cd docs/website/
> $ ~/tmp/ssi-server/ssi_server 8000 &
> $ firefox http:/localhost:8000/
Neat. I normally just open the html file manually, which also kind of
works for most things (not layout obviously).
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2020-01-27 16:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-24 10:37 [Buildroot] [PATCH] docs/website: add commercial support section with Mind Arnout Vandecappelle
2020-01-26 15:42 ` Yann E. MORIN
2020-01-27 16:49 ` Peter Korsgaard [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-02-05 15:08 Arnout Vandecappelle
2020-02-05 15:16 ` Romain Naour
2020-02-20 20:34 ` 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=875zgwsv35.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