From: Saul Wold <saul.wold@intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] documentation audit script
Date: Fri, 28 Oct 2011 07:39:49 +0200 [thread overview]
Message-ID: <4EAA4025.2010709@intel.com> (raw)
In-Reply-To: <cover.1319580412.git.scott.a.garman@intel.com>
On 10/26/2011 12:12 AM, Scott Garman wrote:
> Hello,
>
> I've been using this script to perform audits of which packages
> are producing documentation, and feel it's long overdue for this
> to be added to the git tree. So here it is.
>
> The following changes since commit f586aaa8d00361a9597a546d665077c75cf4d520:
>
> libxml-parser-perl, libxml-simple-perl, expat, sgmlspl-native, git: bump PR to rebuild after perl upgrade (2011-10-25 08:36:01 +0100)
>
> are available in the git repository at:
> git://git.yoctoproject.org/poky-contrib sgarman/docaudit-script
> http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=sgarman/docaudit-script
>
> Scott Garman (1):
> documentation-audit.sh: script for auditing documentation build
> status
>
> scripts/contrib/documentation-audit.sh | 92 ++++++++++++++++++++++++++++++++
> 1 files changed, 92 insertions(+), 0 deletions(-)
> create mode 100755 scripts/contrib/documentation-audit.sh
>
Can you please run this and generate a report.
Thanks
Sau!
next prev parent reply other threads:[~2011-10-28 5:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-25 22:12 [PATCH 0/1] documentation audit script Scott Garman
2011-10-25 22:12 ` [PATCH 1/1] documentation-audit.sh: script for auditing documentation build status Scott Garman
2011-10-28 5:39 ` Saul Wold [this message]
2011-10-28 23:35 ` [PATCH 0/1] documentation audit script Scott Garman
2011-11-02 0:32 ` Saul Wold
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=4EAA4025.2010709@intel.com \
--to=saul.wold@intel.com \
--cc=openembedded-core@lists.openembedded.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