Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Proposal to remove patches from patchwork, or find adopters
Date: Thu, 7 May 2015 12:30:11 +0200	[thread overview]
Message-ID: <20150507123011.5051f113@free-electrons.com> (raw)
In-Reply-To: <CAHXCMMJ7jLEZps8AnGkTuhVvhxmA0M2FpWB+VpOo863vkMfepQ@mail.gmail.com>

Hello,

On Thu, 7 May 2015 12:19:36 +0200, Samuel Martin wrote:

> >  * [v3] autobuilder: branch support
> Already in my todo list

Maybe we should mark this patch as superseded, since you already resent
a new version of it?

> >  * [v1] Python script to check package version
> >  * RFC: [PATCH 1/1] check-updates.py: Adds CVE check
> In my todo list as well.

Did you sync with Maxime Hadjinlian on this? He also started to work on
this topic a while ago. Make sure to not duplicate efforts here.

Thanks,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2015-05-07 10:30 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06 21:53 [Buildroot] Proposal to remove patches from patchwork, or find adopters Thomas Petazzoni
2015-05-06 22:10 ` Alexey Brodkin
2015-05-06 22:52 ` Emeric Vigier
2015-05-06 23:59 ` Jeremy Kerr
2015-05-07  3:42 ` Baruch Siach
2015-05-07  5:48 ` Bernd Kuhls
2015-05-07  6:54 ` jordi montagne
2015-05-11 14:25   ` jean burgat
2015-05-07  8:13 ` Jérôme Pouiller
2015-05-07  8:21 ` Nathaniel Roach
2015-05-07  9:34 ` Károly Kasza
2015-05-07  9:45 ` Will Wagner
2015-05-07 10:19 ` Samuel Martin
2015-05-07 10:30   ` Thomas Petazzoni [this message]
2015-05-07 11:14 ` Carlos Santos
2015-05-15 18:28   ` Carlos Santos
2015-05-15 20:14     ` Carlos Santos
2015-05-16  8:37       ` Thomas Petazzoni
2015-05-08  1:20 ` Zhangjian
2015-05-08 13:42 ` Maxime Hadjinlian
2015-05-10 10:00 ` Thomas De Schampheleire
2015-05-29 15:08   ` Thomas De Schampheleire
2015-05-11 15:11 ` Steve Calfee

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=20150507123011.5051f113@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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