From: Johannes Berg <johannes@sipsolutions.net>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: Re: [PATCH] Documentation: fix DOCBOOKS=... building
Date: Sat, 28 Jul 2012 13:26:35 +0200 [thread overview]
Message-ID: <1343474795.4980.4.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <5013162C.9030606@xenotime.net>
On Fri, 2012-07-27 at 15:29 -0700, Randy Dunlap wrote:
> On 06/13/2012 01:43 AM, Johannes Berg wrote:
>
> > From: Johannes Berg <johannes.berg@intel.com>
> >
> > Prior to
> > commit 4266129964b8238526936d723de65b419d8069c6
> > Author: Mauro Carvalho Chehab <mchehab@redhat.com>
> > Date: Tue May 31 16:27:44 2011 -0300
> >
> > [media] DocBook: Move all media docbook stuff into its own directory
> >
> > it was possible to build only a single (or more)
> > book(s) by calling, for example
> > make htmldocs DOCBOOKS=80211.xml
> >
> > This now fails:
> > cp: target `.../Documentation/DocBook//media_api' is not a directory
> >
> > Ignore errors from that copy to make this possible again.
> >
> > Cc: Mauro Carvalho Chehab <mchehab@redhat.com>
> > Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> > ---
> > I complained about this a long time ago, but now it finally bothered me
> > enough to fix it ... :-)
>
>
> Thanks.
>
> Acked-by: Randy Dunlap <rdunlap@xenotime.net>
Can you apply it somewhere, or should I send it to Andrew, or do you
have any other ideas?
johannes
next prev parent reply other threads:[~2012-07-28 11:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 8:43 [PATCH] Documentation: fix DOCBOOKS=... building Johannes Berg
2012-07-27 22:29 ` Randy Dunlap
2012-07-28 11:26 ` Johannes Berg [this message]
2012-07-28 15:05 ` Randy Dunlap
2012-07-28 16:48 ` Johannes Berg
2012-07-29 0:33 ` Rob Landley
2012-07-30 0:16 ` Mauro Carvalho Chehab
-- strict thread matches above, loose matches on Subject: below --
2014-05-20 13:12 Johannes Berg
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=1343474795.4980.4.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
--cc=rdunlap@xenotime.net \
/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;
as well as URLs for NNTP newsgroup(s).