From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] chrony: Update to 3.4
Date: Sun, 23 Sep 2018 21:06:30 +0200 [thread overview]
Message-ID: <20180923210630.18542c83@windsurf> (raw)
In-Reply-To: <20180921153516.31459-1-ferdinand@ombud.nl>
Hello,
On Fri, 21 Sep 2018 17:35:16 +0200, Ferdinand van Aartsen wrote:
> Patch 0002-util-fall-back-to-reading-dev-urandom-when-getrandom.patch
> was applied upstream in this version, so it can be deleted.
>
> Signed-off-by: Ferdinand van Aartsen <ferdinand@ombud.nl>
> ---
> Changes v2 -> v3:
> - Fix commit style
Applied to master, thanks. Only minor nits are on the commit title:
- We prefer without capitalization, i.e "update to..."
- For version bumps, we generally use "bump to version XYZ" as the
commit title.
I fixed up the commit title before applying, so those comments are
really for your next contributions! :-)
Thanks again,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-09-23 19:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 15:35 [Buildroot] [PATCH v3 1/1] chrony: Update to 3.4 Ferdinand van Aartsen
2018-09-23 19:06 ` 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=20180923210630.18542c83@windsurf \
--to=thomas.petazzoni@bootlin.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