All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Graeme Smecher <gsmecher@threespeedlogic.com>,
	Asaf Kahlon <asafka7@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH v5 1/1] package/python-orjson: bump to version 3.7.7
Date: Sun, 24 Jul 2022 14:18:04 +0200	[thread overview]
Message-ID: <20220724141804.139206ab@windsurf> (raw)
In-Reply-To: <20220724082928.196217-1-james.hilliard1@gmail.com>

Hello James,

On Sun, 24 Jul 2022 02:29:28 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:

> Convert package to use python infrastructure instead of cargo
> infrastructure.
> 
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>
> ----

The separator to use is "---" not "----". If you use "---", git am
preserves what's after the "----" in the commit, which is not what we
want.

> Changes v4 -> v5:
>   - rebase
> Changes v3 -> v4:
>   - update to 3.7.7
> ---
>  package/python-orjson/python-orjson.hash |  5 +++--
>  package/python-orjson/python-orjson.mk   | 24 ++++++++++++------------
>  2 files changed, 15 insertions(+), 14 deletions(-)

I've applied the patch after splitting it: first the conversion to
python-package, then the version bump.

Thanks for the help on IRC to iron out the issues!

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2022-07-24 12:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-24  8:29 [Buildroot] [PATCH v5 1/1] package/python-orjson: bump to version 3.7.7 James Hilliard
2022-07-24 12:18 ` Thomas Petazzoni via buildroot [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=20220724141804.139206ab@windsurf \
    --to=buildroot@buildroot.org \
    --cc=asafka7@gmail.com \
    --cc=gsmecher@threespeedlogic.com \
    --cc=james.hilliard1@gmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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.