From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] LIBLO : bump version to 0.29
Date: Mon, 12 Feb 2018 21:05:00 +0100 [thread overview]
Message-ID: <20180212210500.1832421b@windsurf.lan> (raw)
In-Reply-To: <CA+bRTvDn01oj1dD0NSDaOif8DPSFWLyCjFCGZu8Z=+W_zc_dtA@mail.gmail.com>
Hello,
On Sun, 11 Feb 2018 17:25:25 +0100, Alex Baldwin wrote:
> > In any case, if you do a patch against liblo, don't forget to submit it
> > upstream.
>
> When submitting this patch should I include it as V3 (as V2 failed),
> with all the original patches and ammend the changlog or simply just
> submit the new changes?
As replied to your new submission: you should have sent just the new
changes, because the liblo package has been applied to the next branch
already (which is why it was tested by our autobuilders, and why you
received e-mails about build failures).
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
http://bootlin.com
prev parent reply other threads:[~2018-02-12 20:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 19:37 [Buildroot] [PATCH v2 1/1] LIBLO : bump version to 0.29 Alex B
2018-02-08 19:37 ` Alex B
2018-02-08 22:04 ` Thomas Petazzoni
2018-02-10 16:19 ` Alex Baldwin
2018-02-10 17:45 ` Thomas Petazzoni
2018-02-11 16:25 ` Alex Baldwin
2018-02-12 20:05 ` 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=20180212210500.1832421b@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