All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] ccache dependency issues
Date: Thu, 1 Aug 2013 14:54:26 +0200	[thread overview]
Message-ID: <20130801145426.1dc22f4f@skate> (raw)
In-Reply-To: <CAAXf6LXXukE6yzOEC-U7vVEXq9mnkmjrG8M22=Ou00oVZ2VNJw@mail.gmail.com>

Dear Thomas De Schampheleire,

On Thu, 1 Aug 2013 14:51:32 +0200, Thomas De Schampheleire wrote:

> > That's why I've NAKed additional 'hacks' such as
> > http://patchwork.ozlabs.org/patch/257372/ in the past. BTW, I think
> > moving ccache into the dependencies will avoid the need for this patch
> > 257372, and then we can apply http://patchwork.ozlabs.org/patch/257374/
> > and http://patchwork.ozlabs.org/patch/257375/.
> 
> Ok, sounds good.
> I'll try to create a patch soon, or if you want to do it that's fine
> by me as well.

If you can do it, that'd be great. I'd like to keep some time to merge
a few more things, and then do the -rc1 release after updating the
CHANGES file. So I won't have much time to look at this myself.

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-08-01 12:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-01  9:26 [Buildroot] ccache dependency issues Thomas De Schampheleire
2013-08-01  9:35 ` Thomas Petazzoni
2013-08-01 10:08   ` Thomas De Schampheleire
2013-08-01 11:57     ` Thomas Petazzoni
2013-08-01 12:03       ` Thomas De Schampheleire
2013-08-01 12:07         ` Thomas Petazzoni
2013-08-01 12:51           ` Thomas De Schampheleire
2013-08-01 12:54             ` Thomas Petazzoni [this message]
2013-08-01 21:29               ` 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=20130801145426.1dc22f4f@skate \
    --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 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.