Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2016-08-22
Date: Tue, 23 Aug 2016 15:46:16 +0200	[thread overview]
Message-ID: <20160823154616.19c02486@free-electrons.com> (raw)
In-Reply-To: <ed4e9146-e57c-3045-7642-d786e9574d83@ecagroup.com>

Hello,

On Tue, 23 Aug 2016 13:38:36 +0000, Julien CORJON wrote:

> New daily-mail seems to work well!

It seems! :-)

> Just a comment on that one, you should probably set the mail reply-to 
> field to buildroot at buildroot.org in case developers want to notice 
> directly the community.

Yes, could be an idea, indeed. I'll look into doing this. Thanks for
the suggestion!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

      reply	other threads:[~2016-08-23 13:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160823093410.971F8109354@stock.ovh.net>
2016-08-23 13:38 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2016-08-22 Julien CORJON
2016-08-23 13:46   ` Thomas Petazzoni [this message]

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=20160823154616.19c02486@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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