All of lore.kernel.org
 help / color / mirror / Atom feed
From: Cam Hutchison <camh@xdna.net>
To: buildroot@busybox.net
Subject: [Buildroot] Patchwork cleanup week #24
Date: Fri, 1 Jul 2016 09:51:07 +1000	[thread overview]
Message-ID: <CABa6e=rKdzZeTmeK8w4F6Bv7w7XTrq+d3sdJCEmPxWvMRWwvJw@mail.gmail.com> (raw)
In-Reply-To: <CABa6e=rAQ-Gm4BB4WdcB-wjY641sbv96tQ3G4hiUm8JwOhLfWw@mail.gmail.com>

On 22 June 2016 at 16:14, Cam Hutchison <camh@xdna.net> wrote:
> On 16 June 2016 at 06:06, Thomas Petazzoni
> <thomas.petazzoni@free-electrons.com> wrote:
>>
>> Hello,
>>
>> The previous patchwork cleanup period being over, it's time to start
>> the second period, with 10 other patches. We're on June 15th, so I'll
>> give people until June 30th to react on the following patches. If
>> there's no reaction, like no interest from either the original
>> submitter nor any other Buildroot developer, the patch will be marked
>> Rejected on June 30th.
>>
>> If you are in To: of this e-mail, then one or several of the patches
>> below have been authored by you, so you should be interested :-)
>>
>> [...]
>>
>>  9. overlay: Add archive-based (tar) rootfs overlays
>>     http://patchwork.ozlabs.org/patch/610752/
>
> I did post this patch, but I'm not sure how I'm meant to react to this
> email. Do I just wait for someone to comment and if they don't, it
> gets rejected?

So June 30th is here and I'm still not sure what I'm meant to do.

Does my patch just get marked as rejected now?

  reply	other threads:[~2016-06-30 23:51 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-15 20:06 [Buildroot] Patchwork cleanup week #24 Thomas Petazzoni
     [not found] ` <CAJsd3zJkzAUJhvBPJ9hdQ60YmjSjuB7sahptmLFx6-1V70fLAg@mail.gmail.com>
2016-06-15 21:18   ` Thomas Petazzoni
2016-06-16  7:18 ` Thomas De Schampheleire
2016-06-16  7:32   ` Thomas Petazzoni
2016-06-16  9:52     ` Thomas De Schampheleire
2016-06-16  9:56       ` Thomas Petazzoni
2016-06-16 17:30         ` Yann E. MORIN
2016-06-16 17:23       ` Yann E. MORIN
2016-06-18 20:56         ` Thomas Petazzoni
2016-06-18 14:14 ` Romain Naour
     [not found] ` <4209f432-0fbd-8d44-7194-c99829f66e2e@smile.fr>
2016-06-22  5:45   ` Alexey Brodkin
2016-06-24  7:24     ` Vlad Zakharov
2016-06-24  7:32       ` Thomas Petazzoni
2016-06-24  9:13         ` Alexey Brodkin
2016-06-24  9:15           ` Thomas Petazzoni
2016-06-24  9:17             ` Alexey Brodkin
2016-07-01  7:59       ` Romain Naour
2016-06-22  6:14 ` Cam Hutchison
2016-06-30 23:51   ` Cam Hutchison [this message]
2016-07-01  7:01     ` Thomas Petazzoni
2016-06-22 20:57 ` Arnout Vandecappelle
2016-06-26 11:07 ` Jörg Krause
2016-06-26 12:53   ` Thomas Petazzoni
2016-07-24 20:23 ` Thomas Petazzoni

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='CABa6e=rKdzZeTmeK8w4F6Bv7w7XTrq+d3sdJCEmPxWvMRWwvJw@mail.gmail.com' \
    --to=camh@xdna.net \
    --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.