From: Thomas Huth <huth@tuxfamily.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] package/ascii-invaders: Add the game ascii-invaders
Date: Tue, 28 May 2019 08:18:22 +0200 [thread overview]
Message-ID: <20190528081822.29f67611@thl530.multi.box> (raw)
In-Reply-To: <20190527173200.2408159d@windsurf>
Am Mon, 27 May 2019 17:32:00 +0200
schrieb Thomas Petazzoni <thomas.petazzoni@bootlin.com>:
> Hello Thomas,
>
> On Mon, 27 May 2019 17:22:09 +0200
> Thomas Huth <huth@tuxfamily.org> wrote:
>
> > >> +$(eval $(generic-package))
> > >>
> > >
> > > Friendly *ping*
> >
> > Ping^2 ?
>
> Sorry for the lack of answer/feedback. However, sending pings is not
> really useful: your patch cannot be lost because we have a tool
> tracking all patches sent to the mailing list,
> http://patchwork.ozlabs.org/project/buildroot/list/.
Ah, alright. Sorry, so far I mainly participated in projects where one
was supposed to "ping" on the patches after a couple of weeks. Using
patchwork is certainly the better idea.
> As long as your
> patch is still there, it is not lost. The queue of patches is
> currently 227 patches, so your best chance to get your patch reviewed
> and merged is to help by reviewing/testing patches submitted by
> others :-)
Ok, I'll have a try.
Thomas
next prev parent reply other threads:[~2019-05-28 6:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 8:11 [Buildroot] [PATCH v2] package/ascii-invaders: Add the game ascii-invaders Thomas Huth
2019-05-13 15:19 ` Thomas Huth
2019-05-27 15:22 ` Thomas Huth
2019-05-27 15:32 ` Thomas Petazzoni
2019-05-28 6:18 ` Thomas Huth [this message]
2019-06-03 18:29 ` Gilles Talis
2019-08-03 13:22 ` Peter Korsgaard
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=20190528081822.29f67611@thl530.multi.box \
--to=huth@tuxfamily.org \
--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 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.