From: Saul Wold <saul.wold@intel.com>
To: Scott Garman <scott.a.garman@intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 0/2] build libuser documentation
Date: Fri, 25 Feb 2011 09:30:54 -0800 [thread overview]
Message-ID: <4D67E74E.7030000@intel.com> (raw)
In-Reply-To: <cover.1298592962.git.scott.a.garman@intel.com>
On 02/24/2011 05:07 PM, Scott Garman wrote:
> From: Scott Garman<scott.a.garman@intel.com>
>
> Hi Saul,
>
> This pull request fixes bug #213, allowing the documentation for
> libuser to be generated.
>
> Pull URL: git://git.pokylinux.org/poky-contrib.git
> Branch: sgarman/libuser-fix
> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=sgarman/libuser-fix
>
> Thanks,
> Scott Garman<scott.a.garman@intel.com>
> ---
>
>
> Scott Garman (2):
> linuxdoc-tools-native: new recipe v0.99.6
> libuser: enable documentation
>
> .../linuxdoc-tools-native/disable_sgml2rtf.patch | 49 ++++++++++++++++++++
> .../linuxdoc-tools/linuxdoc-tools-native_0.9.66.bb | 21 ++++++++
> .../libuser/libuser-0.57.1/disable-sgml-doc.patch | 18 -------
> meta/recipes-extended/libuser/libuser_0.57.1.bb | 9 ++--
> 4 files changed, 74 insertions(+), 23 deletions(-)
> create mode 100644 meta/recipes-devtools/linuxdoc-tools/linuxdoc-tools-native/disable_sgml2rtf.patch
> create mode 100644 meta/recipes-devtools/linuxdoc-tools/linuxdoc-tools-native_0.9.66.bb
> delete mode 100644 meta/recipes-extended/libuser/libuser-0.57.1/disable-sgml-doc.patch
>
> _______________________________________________
> poky mailing list
> poky@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/poky
>
Merged into Master
Thanks
Sau!
prev parent reply other threads:[~2011-02-25 17:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 1:07 [PATCH 0/2] build libuser documentation Scott Garman
2011-02-25 1:07 ` [PATCH 1/2] linuxdoc-tools-native: new recipe v0.99.6 Scott Garman
2011-02-25 1:07 ` [PATCH 2/2] libuser: enable documentation Scott Garman
2011-02-25 17:30 ` Saul Wold [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=4D67E74E.7030000@intel.com \
--to=saul.wold@intel.com \
--cc=poky@yoctoproject.org \
--cc=scott.a.garman@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 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.