All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Raphaël Mélotte" <raphael.melotte@mind.be>
Cc: Ricardo Martincoski <ricardo.martincoski@gmail.com>,
	buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] support/testing: add new test for python-jmespath
Date: Fri, 22 Jul 2022 23:22:10 +0200	[thread overview]
Message-ID: <20220722232210.742df319@windsurf> (raw)
In-Reply-To: <20220614164755.716683-1-raphael.melotte@mind.be>

On Tue, 14 Jun 2022 18:47:53 +0200
Raphaël Mélotte <raphael.melotte@mind.be> wrote:

> Add a new rudimentary test inspired by the examples from jmespath's
> README file ([1]).
> 
> [1]: https://github.com/jmespath/jmespath.py/blob/develop/README.rst
> 
> Signed-off-by: Raphaël Mélotte <raphael.melotte@mind.be>
> ---
>  .../testing/tests/package/sample_python_jmespath.py  |  4 ++++
>  .../testing/tests/package/test_python_jmespath.py    | 12 ++++++++++++
>  2 files changed, 16 insertions(+)
>  create mode 100644 support/testing/tests/package/sample_python_jmespath.py
>  create mode 100644 support/testing/tests/package/test_python_jmespath.py

Thanks, both applied to master. On the first patch, I also added you to
the DEVELOPERS file for the new test case (thanks for adding it!).

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

      parent reply	other threads:[~2022-07-22 21:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 16:47 [Buildroot] [PATCH 1/2] support/testing: add new test for python-jmespath Raphaël Mélotte
2022-06-14 16:47 ` [Buildroot] [PATCH 2/2] package/python-jmespath: bump to version 1.0.0 Raphaël Mélotte
2022-07-22 21:22 ` 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=20220722232210.742df319@windsurf \
    --to=buildroot@buildroot.org \
    --cc=raphael.melotte@mind.be \
    --cc=ricardo.martincoski@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.