From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] avahi: add hash file
Date: Wed, 11 Mar 2015 18:40:36 -0300 [thread overview]
Message-ID: <5500B654.7010800@zacarias.com.ar> (raw)
In-Reply-To: <5500A9FB.3090307@dawncrow.de>
On 03/11/2015 05:47 PM, Andr? Hentschel wrote:
> This fixes the issue, but we should take care if the website is not going back up again
In theory it's a temporary fluke, we'll see though...
Regards.
next prev parent reply other threads:[~2015-03-11 21:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 19:26 [Buildroot] [PATCH] avahi: add hash file Gustavo Zacarias
2015-03-11 20:47 ` André Hentschel
2015-03-11 21:17 ` Peter Korsgaard
2015-03-11 21:40 ` Gustavo Zacarias [this message]
2015-03-11 21:16 ` 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=5500B654.7010800@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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