All of lore.kernel.org
 help / color / mirror / Atom feed
From: Danomi Manchego <danomimanchego123@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Patchwork cleanup #8: triaging proposal
Date: Sun, 13 Apr 2014 21:02:51 -0400	[thread overview]
Message-ID: <CANxTyt64XrOYPar2V-D_uUEWYixHBGep5UNFbijQn+HdB-Pheg@mail.gmail.com> (raw)
In-Reply-To: <CAAXf6LUKOuGpMV0uzR3gDM++pOu9Ldtb=6FfTGHqXjMdpvCfSA@mail.gmail.com>

All,

On Sun, Apr 13, 2014 at 3:43 PM, Thomas De Schampheleire
<patrickdepinguin@gmail.com> wrote:
> [1/3] ccache: change compilercheck to use compiler and toolchain info
> Danomi Manchego <danomimanchego123@gmail.com>
> http://patchwork.ozlabs.org/patch/287383
>
> [2/3] ccache: change default cache directory path to match config setting
> Danomi Manchego <danomimanchego123@gmail.com>
> http://patchwork.ozlabs.org/patch/287384
>
> [3/3] ccache: provide capability to do initial ccache setup
> Danomi Manchego <danomimanchego123@gmail.com>
> http://patchwork.ozlabs.org/patch/287385
>
> Proposal for the above 3: D more work needed. Looking at Arnout's
> comments on the first patch, this needs to be thought through, and a
> final solution is to be implemented. I really think we should improve
> ccache in buildroot, though, so I hope a proper solution can be found.

I believe that Arnout's comments are in regards to the first patch
only.  The second and third patches are actually independent of the
first patch, and each other.  So they can be accepted or rejected on
their own merits.

Regardless - I've taken the first patch as far as I can, and don't
really have the bandwidth to rework it again.  So ... TODO list it is.

Danomi -

  parent reply	other threads:[~2014-04-14  1:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-13 19:43 [Buildroot] Patchwork cleanup #8: triaging proposal Thomas De Schampheleire
2014-04-13 19:48 ` Thomas Petazzoni
2014-04-15  0:08   ` Ryan Barnett
2014-04-14  1:02 ` Danomi Manchego [this message]
2014-05-01 18:37 Marcelo Gutierrez
2014-05-05  7:03 ` Arnaud Aujon
2014-05-05  7:26 ` Thomas De Schampheleire

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=CANxTyt64XrOYPar2V-D_uUEWYixHBGep5UNFbijQn+HdB-Pheg@mail.gmail.com \
    --to=danomimanchego123@gmail.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 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.