Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Luca Ceresoli <luca@lucaceresoli.net>
To: buildroot@busybox.net
Subject: [Buildroot] List of pending patches: what to do?
Date: Mon, 19 Aug 2013 12:35:36 +0200	[thread overview]
Message-ID: <5211F4F8.7060800@lucaceresoli.net> (raw)
In-Reply-To: <20130731191415.545f7dff@skate>

Thomas,

Thomas Petazzoni wrote:
> Hello,
>
> We currently have 228 pending patches in our patchwork at
> http://patchwork.ozlabs.org/project/buildroot/list/. Many patches are
> old and should be adopted to be cleaned up and resubmitted, or maybe
> need to be rejected but after some community discussion.
>
> In order to help reducing the backlog of patches, I'm pasting below the
> entire list of patches with their title and direct link to patchwork.
> What I'm interested in is people replying to this e-mail and giving
> their opinion about some of the patches (don't try to look at all of
> them, but at least a few of them). Opinions can be: we should reject,
> I'm interested in adopting the patch and refreshing it, the patch is
> interesting but needs this and that to be merged, etc.
>
> Thanks for your help!
...
> http://patchwork.ozlabs.org/patch/230289 [v2] Enable ccache for cmake packages

This led to a fairly long discussion with Samuel, you and me on howit
should be implemented.You suggested it should be done in the toolchain
wrappers. Thedetails were not clear to me, but it was definitely nothing
similar to this patch.

So probably it should be dropped from patchwork.

Note: the discussion is not fully visible in patchwork, see it here:
http://lists.busybox.net/pipermail/buildroot/2013-March/068306.html

FWIW, I'm not even using that patch. Instead I'm using the v1
(http://lists.busybox.net/pipermail/buildroot/2013-March/068306.html)
which added a stupid shell wrapper around TARGET_CC/_CXX. It's probably
not very nice but it's simple and it just works.

Luca

      parent reply	other threads:[~2013-08-19 10:35 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-31 17:14 [Buildroot] List of pending patches: what to do? Thomas Petazzoni
2013-07-31 17:18 ` Thomas Petazzoni
2013-07-31 20:44   ` Yann E. MORIN
2013-08-01  5:39     ` Thomas Petazzoni
2013-07-31 17:51 ` Gustavo Zacarias
2013-08-01  5:50   ` Thomas Petazzoni
2013-07-31 20:45 ` Thomas De Schampheleire
2013-07-31 20:57   ` Yann E. MORIN
2013-08-01  5:59   ` Thomas Petazzoni
2013-08-01 20:24     ` Yann E. MORIN
2013-07-31 20:55 ` Yann E. MORIN
2013-08-01  6:04   ` Thomas Petazzoni
2013-07-31 22:13 ` Samuel Martin
2013-07-31 22:20   ` Yann E. MORIN
2013-08-01 16:23   ` Thomas Petazzoni
2013-08-01 21:30     ` Samuel Martin
2013-08-02  8:33       ` Thomas De Schampheleire
2013-08-02  8:50         ` Thomas Petazzoni
2013-08-02  9:09           ` Thomas De Schampheleire
2013-08-02  9:10             ` Thomas Petazzoni
2013-08-02  9:27               ` Thomas De Schampheleire
2013-08-12 21:01         ` Arnout Vandecappelle
2013-08-01  2:52 ` Danomi Manchego
2013-08-01  6:13   ` Thomas Petazzoni
2013-08-01 20:14     ` Yann E. MORIN
2013-08-01  6:54 ` Simon Dawson
2013-08-01  7:41   ` Thomas Petazzoni
2013-08-01 16:16 ` Thomas Petazzoni
2013-08-02  8:10 ` Jérôme Pouiller
2013-08-02 11:11 ` Patrick Ziegler
2013-08-02 11:17   ` Thomas Petazzoni
2013-08-19 10:35 ` Luca Ceresoli [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=5211F4F8.7060800@lucaceresoli.net \
    --to=luca@lucaceresoli.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox