All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Chris Tapp <opensource@keylevel.com>
Cc: yocto@yoctoproject.org
Subject: Re: bbappend - Where should my file be?
Date: Wed, 31 Aug 2011 21:01:18 +0100	[thread overview]
Message-ID: <1314820878.5939.495.camel@rex> (raw)
In-Reply-To: <A03B490E-95AF-4E98-816C-A74154CE950E@keylevel.com>

On Wed, 2011-08-31 at 20:33 +0100, Chris Tapp wrote:
> Sorry for the delay in looking at this again.
> 
> I can't re-create the behaviour here either, though it was repeatable  
> before. However, since then I've made quite a few changes to the  
> recipe and done a complete re-build.
> 
> It was also failing with the correct paths - I was trying all sorts of  
> combinations when the correct one wasn't working!
> 
> I'll try and do some more testing here (with what I think the recipe  
> was at the time) to see if I can get it to show again. I've only got a  
> slow build machine, so it may take a while ;-)

Ok, in the meantime I've resolved the bug as worksforme since we're
unable to reproduce. Please do open (or reopen) one if you can reproduce
the problem though, I'd be interested to get to the bottom of it.

Cheers,

Richard



      reply	other threads:[~2011-08-31 20:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-11 23:51 bbappend - Where should my file be? Chris Tapp
2011-08-11 23:57 ` Scott Garman
2011-08-12  0:28   ` Bruce Ashfield
2011-08-12  8:20     ` Chris Tapp
2011-08-12 12:59       ` Bruce Ashfield
2011-08-12 19:48         ` Chris Tapp
2011-08-17 16:32           ` Joshua Lock
2011-08-30 18:07 ` Richard Purdie
2011-08-31 19:33   ` Chris Tapp
2011-08-31 20:01     ` Richard Purdie [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=1314820878.5939.495.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=opensource@keylevel.com \
    --cc=yocto@yoctoproject.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 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.