From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] nilfs-utils: fix build with static toolchains
Date: Mon, 8 Jan 2018 09:57:26 +0100 [thread overview]
Message-ID: <20180108095726.0e59875a@windsurf> (raw)
In-Reply-To: <20180108083533.GA24186@airbook.vandijck-laurijssen.be>
Hello,
On Mon, 8 Jan 2018 09:35:33 +0100, Kurt Van Dijck wrote:
> > >
> > > Nit: when sending a new version of a patch, it is strongly recommended
> > > to use [PATCH v2], [PATCH v3], and include a changelog...
> >
> > Also, when you're fixing autobuilder failures, your commit log should
> > include a reference to one such failure. Something like this:
> >
> > Fixes:
> >
> > http://autobuild.buildroot.org/results/<hash>/
> >
> > Thanks!
>
> I see. Will I resend?
Well, I made other comments in a different e-mail, which indeed require
a resend.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2018-01-08 8:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-07 20:39 [Buildroot] [PATCH] nilfs-utils: fix build with static toolchains Kurt Van Dijck
2018-01-07 22:29 ` Thomas Petazzoni
2018-01-07 22:42 ` Thomas Petazzoni
2018-01-08 8:35 ` Kurt Van Dijck
2018-01-08 8:57 ` Thomas Petazzoni [this message]
2018-01-18 13:33 ` Thomas Petazzoni
2018-01-18 19:54 ` Kurt Van Dijck
-- strict thread matches above, loose matches on Subject: below --
2018-01-03 20:15 Kurt Van Dijck
2018-01-03 20:33 ` Thomas Petazzoni
2018-01-04 8:14 ` Kurt Van Dijck
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=20180108095726.0e59875a@windsurf \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.