From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] keepalived: bump to version 1.4.1
Date: Sat, 10 Feb 2018 10:14:09 +0100 [thread overview]
Message-ID: <20180210101409.436a13d6@windsurf.lan> (raw)
In-Reply-To: <20180210101340.1c79fb16@windsurf.lan>
Hello,
On Sat, 10 Feb 2018 10:13:40 +0100, Thomas Petazzoni wrote:
> Hello,
>
> On Fri, 9 Feb 2018 12:28:47 +0200, Baruch Siach wrote:
> > Add license file hash.
> >
> > Cc: Ilias Apalodimas <apalos@gmail.com>
> > Signed-off-by: Baruch Siach <baruch@tkos.co.il>
> > ---
> > package/keepalived/keepalived.hash | 3 ++-
> > package/keepalived/keepalived.mk | 2 +-
> > 2 files changed, 3 insertions(+), 2 deletions(-)
>
> Applied to master, thanks.
Not at all: I replied to the wrong patch. I haven't applied this one
yet, and it should anyway be applied to the next branch.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
next prev parent reply other threads:[~2018-02-10 9:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 10:28 [Buildroot] [PATCH] keepalived: bump to version 1.4.1 Baruch Siach
2018-02-10 9:13 ` Thomas Petazzoni
2018-02-10 9:14 ` Thomas Petazzoni [this message]
2018-02-14 21:05 ` Thomas Petazzoni
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=20180210101409.436a13d6@windsurf.lan \
--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