From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Sen Hastings <sen@phobosdpl.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 0/2] support/scripts/pkg-stats: fix row/column ordering issues
Date: Thu, 28 Jul 2022 09:30:57 +0200 [thread overview]
Message-ID: <20220728093057.070f5acc@windsurf> (raw)
In-Reply-To: <20220728021444.135820-1-sen@phobosdpl.com>
Hello Sen,
On Wed, 27 Jul 2022 21:14:42 -0500
Sen Hastings <sen@phobosdpl.com> wrote:
> This is because I'm not sure whether you are supposed to rev patches that
> have already been committed.
Nope, you are expected to do exactly what you did: rebase your
remaining contributions on the latest master, so that you resend only
the remaining of the work that has not been merged so far.
> Sen Hastings (2):
> support/scripts/pkg-stats: fix rows with duplicate package class names
> support/scripts/pkg-stats: fixed sortGrid() performance
Both applied, thanks a lot for the quick turnaround!
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
prev parent reply other threads:[~2022-07-28 7:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 2:14 [Buildroot] [PATCH 0/2] support/scripts/pkg-stats: fix row/column ordering issues Sen Hastings
2022-07-28 2:14 ` [Buildroot] [PATCH 1/2] support/scripts/pkg-stats: fix duplicate package class names across rows Sen Hastings
2022-07-28 2:14 ` [Buildroot] [PATCH 2/2] support/scripts/pkg-stats: fixed sortGrid() performance Sen Hastings
2022-07-28 7:30 ` 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=20220728093057.070f5acc@windsurf \
--to=buildroot@buildroot.org \
--cc=sen@phobosdpl.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.