Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3] Some more games: XorCurses, ASCII-Invaders and Frotz
Date: Sun, 17 Mar 2019 16:16:36 +0100	[thread overview]
Message-ID: <20190317161636.3fca767a@windsurf> (raw)
In-Reply-To: <1d8dac6e-1cca-9f19-bd81-445ba43d792b@tuxfamily.org>

Hello,

On Thu, 7 Mar 2019 12:16:20 +0100
Thomas Huth <huth@tuxfamily.org> wrote:

> Any comments? Are the patches not suitable for buildroot? No problem,
> just let me know and I'll shut up ;-) ... or is it that just nobody has
> enough spare time for a review?

Gilles Talis did a review of your patches on March 16. When you have
some time, could you take into account your comments, and send a v2 of
this patch series ?

In the mean time, I'll mark the patches as "Changes Requested" in
patchwork (our patch tracking tool).

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2019-03-17 15:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-23 20:56 [Buildroot] [PATCH 0/3] Some more games: XorCurses, ASCII-Invaders and Frotz Thomas Huth
2019-02-23 20:56 ` [Buildroot] [PATCH 1/3] package/xorcurses: new package Thomas Huth
2019-03-16 16:57   ` Gilles Talis
2019-04-22  5:55     ` Thomas Huth
2019-06-03 18:22       ` Gilles Talis
2019-02-23 20:56 ` [Buildroot] [PATCH 2/3] package/ascii-invaders: " Thomas Huth
2019-03-16 17:04   ` Gilles Talis
2019-02-23 20:56 ` [Buildroot] [PATCH 3/3] package/frotz: " Thomas Huth
2019-03-16 17:15   ` Gilles Talis
2019-03-07 11:16 ` [Buildroot] [PATCH 0/3] Some more games: XorCurses, ASCII-Invaders and Frotz Thomas Huth
2019-03-17 15:16   ` Thomas Petazzoni [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=20190317161636.3fca767a@windsurf \
    --to=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox