Openembedded Bitbake Development
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>
Cc: "bitbake-devel@lists.openembedded.org"
	<bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH 2/2] bitbake-user-manual-intro.xml: update for dump-signatures
Date: Mon, 21 Jul 2014 19:18:52 +0100	[thread overview]
Message-ID: <1405966732.22985.104.camel@ted> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB1237983FB63CD@ORSMSX101.amr.corp.intel.com>

On Mon, 2014-07-07 at 06:18 +0000, Rifenbark, Scott M wrote:
> Ok - if there is a problem or changes then let me know.  I have the
> doc changes pushed to poky-contrib/srifenbark/bb-manual only.  Richard
> would have to merge them from there into the upstream bitbake
> repository.

I modified Roberts patch a bit. Could you update the manual based on
that patch? I didn't take the change for the manual you have queued for
this, I'd suggest we create a new one. I did merge everything else in
your bitbake manual branch.

Cheers,

Richard



  reply	other threads:[~2014-07-21 18:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-04  5:39 [PATCH 0/2] bitbake: update help message for dump-signatures Robert Yang
2014-07-04  5:39 ` [PATCH 1/2] " Robert Yang
2014-07-04  7:36   ` Richard Purdie
2014-07-04  8:23     ` Robert Yang
2014-07-04  5:39 ` [PATCH 2/2] bitbake-user-manual-intro.xml: update " Robert Yang
2014-07-07  6:13   ` Rifenbark, Scott M
2014-07-07  6:16     ` Robert Yang
2014-07-07  6:18       ` Rifenbark, Scott M
2014-07-21 18:18         ` Richard Purdie [this message]
2014-07-22  6:50           ` Rifenbark, Scott M
2014-07-22  8:12           ` Robert Yang
2014-07-22  8:35             ` 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=1405966732.22985.104.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=bitbake-devel@lists.openembedded.org \
    --cc=scott.m.rifenbark@intel.com \
    /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