All of lore.kernel.org
 help / color / mirror / Atom feed
From: Charles Hardin <charles.hardin@storagecraft.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/5] package/protobuf: bump to version 3.5.1
Date: Tue, 22 May 2018 17:18:15 +0000	[thread overview]
Message-ID: <AD5C86F9-A62E-4AC7-94C1-D7AC33C6D672@storagecraft.com> (raw)
In-Reply-To: <20180522121101.07546890@windsurf>

Thomas,

On May 22, 2018, at 3:11 AM, Thomas Petazzoni <thomas.petazzoni at bootlin.com<mailto:thomas.petazzoni@bootlin.com>> wrote:

Hello Charles,

On Mon, 21 May 2018 10:53:06 -0700, charles.hardin at storagecraft.com<mailto:charles.hardin@storagecraft.com>
wrote:
From: Martijn de Gouw <martijn.de.gouw at prodrive-technologies.com<mailto:martijn.de.gouw@prodrive-technologies.com>>

GRPC requires protobuf 3.5.0+

Signed-off-by: Martijn de Gouw <martijn.de.gouw at prodrive-technologies.com<mailto:martijn.de.gouw@prodrive-technologies.com>>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni at bootlin.com<mailto:thomas.petazzoni@bootlin.com>>
(cherry picked from commit 454aa2da5e79ec8627f1d66ac640ec7bb04025dc)

Why are you sending this patch? It's already in the next branch. Since
what you're sending is intended for the next branch, you should simply
base your patches on the next branch, and send only what's not yet in
next.



The docs say to rebase against origin/master before submitting a patch not
origin/next. So, it is unclear if we are suppose to submit a patch series that
compiles as a set or a patch series that relies on something already in next.

I erred on a duplicated patch at the beginning to try and make sure it was
understood this patch series requires the bump - else, it won?t compile.

If there is a better a way to do this, then it wasn?t clear from contributing guide.

https://buildroot.org/downloads/manual/manual.html#submitting-patches


I'll mark this patch as Not Applicable in our patch tracking system.

Best regards,

Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com


Charles

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20180522/af1ee5fb/attachment.html>

  reply	other threads:[~2018-05-22 17:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-21 17:53 [Buildroot] [PATCH v2 0/5] add support for gRPC C and C++ bindings charles.hardin at storagecraft.com
2018-05-21 17:53 ` [Buildroot] [PATCH v2 1/5] package/protobuf: bump to version 3.5.1 charles.hardin at storagecraft.com
2018-05-22 10:11   ` Thomas Petazzoni
2018-05-22 17:18     ` Charles Hardin [this message]
2018-05-22 19:10       ` Thomas Petazzoni
2018-05-21 17:53 ` [Buildroot] [PATCH v2 2/5] package/protobuf: add a patch for mips big endian charles.hardin at storagecraft.com
2018-06-28 20:34   ` Thomas Petazzoni
2018-06-28 21:36     ` Charles Hardin
2018-06-28 21:39       ` Thomas Petazzoni
2018-05-21 17:53 ` [Buildroot] [PATCH v2 3/5] package/c-ares: enable the host variant for a c-ares install charles.hardin at storagecraft.com
2018-05-21 17:53 ` [Buildroot] [PATCH v2 4/5] grpc: new package charles.hardin at storagecraft.com
2018-06-28 21:36   ` Thomas Petazzoni
2018-06-28 21:45     ` Charles Hardin
2018-06-28 21:52       ` Thomas Petazzoni
2018-06-28 21:47   ` Thomas Petazzoni
2018-05-21 17:53 ` [Buildroot] [PATCH v2 5/5] package/collectd: allow the grpc plugin to be configured charles.hardin at storagecraft.com

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=AD5C86F9-A62E-4AC7-94C1-D7AC33C6D672@storagecraft.com \
    --to=charles.hardin@storagecraft.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.