Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <philb@gnu.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: openembedded-core <openembedded-core@lists.openembedded.org>
Subject: Re: [RFC PATCH] bitbake.conf: Change WORKDIR to split by PN and version into seperate directories
Date: Fri, 21 Sep 2012 15:27:48 +0100	[thread overview]
Message-ID: <1348237670.15074.234.camel@phil-desktop> (raw)
In-Reply-To: <1348237488.10108.83.camel@ted>

On Fri, 2012-09-21 at 15:24 +0100, Richard Purdie wrote:
> As per the previous patch, this is really a request for comments, I can
> see pros and cons...

I've been using this configuration locally for quite some time (it's
needed for rm_old_works in particular) and it seems to be an improvement
in general.

p.





  reply	other threads:[~2012-09-21 14:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21 14:24 [RFC PATCH] bitbake.conf: Change WORKDIR to split by PN and version into seperate directories Richard Purdie
2012-09-21 14:27 ` Phil Blundell [this message]
2012-09-21 15:18   ` Martin Jansa
2012-09-22 11:43     ` Richard Purdie

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=1348237670.15074.234.camel@phil-desktop \
    --to=philb@gnu.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /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