Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: Asaf Kahlon <asafka7@gmail.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 2/2] package/python-terminaltables: fix build backend
Date: Tue, 11 Jul 2023 10:00:53 +0200	[thread overview]
Message-ID: <20230711100053.1d9d3671@windsurf> (raw)
In-Reply-To: <CADvTj4r7QRpW3NaYQc+_iZ5Y1WnzBeMQsptvtrtTudDc47X12w@mail.gmail.com>

On Tue, 11 Jul 2023 01:35:54 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:

> > So is this patch series modifying python-terminaltables a prerequisite
> > to applying the patch at
> > https://patchwork.ozlabs.org/project/buildroot/patch/20230626181531.2312002-5-james.hilliard1@gmail.com/ ?  
> 
> Yes, it should be applied before that one.

Then, as explained in another e-mail, it should be part of the same
series. Yes, I understand that you sent the series before noticing that
python-terminaltables needed to be changed, and that's fine: send a new
complete iteration of the series with the extra patches.

And for such complicated series, please *always* add a cover letter
that gives some background: what you're trying to do, and what is the
path taken to achieve this.

Thanks!

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

  reply	other threads:[~2023-07-11  8:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27  7:26 [Buildroot] [PATCH 1/2] package/python-poetry-core: new host package James Hilliard
2023-06-27  7:26 ` [Buildroot] [PATCH 2/2] package/python-terminaltables: fix build backend James Hilliard
2023-07-10 18:01   ` Thomas Petazzoni via buildroot
2023-07-10 19:58     ` James Hilliard
2023-07-11  7:32       ` Thomas Petazzoni via buildroot
2023-07-11  7:35         ` James Hilliard
2023-07-11  8:00           ` Thomas Petazzoni via buildroot [this message]
2023-07-11  9:43             ` James Hilliard
2023-07-11  9:54               ` Thomas Petazzoni via buildroot
2023-07-11  9:57                 ` Thomas Petazzoni via buildroot
2023-07-11 10:50                 ` James Hilliard
2023-07-11 12:29                   ` Thomas Petazzoni via buildroot
2023-07-11 14:42                     ` James Hilliard

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=20230711100053.1d9d3671@windsurf \
    --to=buildroot@buildroot.org \
    --cc=asafka7@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox