From: Jani Nikula <jani.nikula@linux.intel.com>
To: Jim Davis <jim.epost@gmail.com>, Jonathan Corbet <corbet@lwn.net>,
linux-doc <linux-doc@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: make cleandocs missing files with v4.9-rc3
Date: Mon, 31 Oct 2016 22:38:02 +0200 [thread overview]
Message-ID: <877f8ol0et.fsf@intel.com> (raw)
In-Reply-To: <CA+r1Zhjr5SCVAroREBv84t9bxDVu5jVJ_Fu=BbVDGNNABdQOuQ@mail.gmail.com>
On Mon, 31 Oct 2016, Jim Davis <jim.epost@gmail.com> wrote:
> On my Ubuntu 16.04 system, make htmldocs works just fine (hurrah!) but
> make cleandocs misses a fair number of files:
>
> HTML Documentation/DocBook/index.html
> jim@krebstar:~/linux-rc$ make cleandocs
> jim@krebstar:~/linux-rc$ git status
> HEAD detached at v4.9-rc3
> nothing to commit, working directory clean
> jim@krebstar:~/linux-rc$ git clean -fdx
> Removing Documentation/DocBook/.alsa-driver-api.xml.cmd
> Removing Documentation/DocBook/.crypto-API.xml.cmd
> Removing Documentation/DocBook/.debugobjects.xml.cmd
> Removing Documentation/DocBook/.deviceiobook.xml.cmd
> Removing Documentation/DocBook/.filesystems.xml.cmd
> Removing Documentation/DocBook/.gadget.xml.cmd
> Removing Documentation/DocBook/.genericirq.xml.cmd
> Removing Documentation/DocBook/.iio.xml.cmd
> Removing Documentation/DocBook/.kernel-api.xml.cmd
> Removing Documentation/DocBook/.kernel-hacking.xml.cmd
> Removing Documentation/DocBook/.kernel-locking.xml.cmd
> Removing Documentation/DocBook/.kgdb.xml.cmd
> Removing Documentation/DocBook/.libata.xml.cmd
> Removing Documentation/DocBook/.librs.xml.cmd
> Removing Documentation/DocBook/.lsm.xml.cmd
> Removing Documentation/DocBook/.mtdnand.xml.cmd
> Removing Documentation/DocBook/.networking.xml.cmd
> Removing Documentation/DocBook/.rapidio.xml.cmd
> Removing Documentation/DocBook/.regulator.xml.cmd
> Removing Documentation/DocBook/.s390-drivers.xml.cmd
> Removing Documentation/DocBook/.scsi.xml.cmd
> Removing Documentation/DocBook/.sh.xml.cmd
> Removing Documentation/DocBook/.tracepoint.xml.cmd
> Removing Documentation/DocBook/.uio-howto.xml.cmd
> Removing Documentation/DocBook/.usb.xml.cmd
> Removing Documentation/DocBook/.w1.xml.cmd
> Removing Documentation/DocBook/.writing-an-alsa-driver.xml.cmd
> Removing Documentation/DocBook/.writing_musb_glue_layer.xml.cmd
> Removing Documentation/DocBook/.writing_usb_driver.xml.cmd
> Removing Documentation/DocBook/.z8530book.xml.cmd
> Removing Documentation/sphinx/cdomain.pyc
> Removing Documentation/sphinx/kernel-doc.pyc
> Removing Documentation/sphinx/kernel_include.pyc
> Removing Documentation/sphinx/load_config.pyc
> Removing Documentation/sphinx/rstFlatTable.pyc
This patch [1] should fix the pyc stuff. I suspect the rest have been
broken forever; will be fixed when the DocBook toolchain gets nuked. ;)
BR,
Jani.
[1] http://lkml.kernel.org/r/1477945781-8354-1-git-send-email-jani.nikula@intel.com
> Removing scripts/.check-lc_ctype.cmd
> Removing scripts/.docproc.cmd
> Removing scripts/basic/.fixdep.cmd
> Removing scripts/basic/fixdep
> Removing scripts/check-lc_ctype
> Removing scripts/docproc
--
Jani Nikula, Intel Open Source Technology Center
prev parent reply other threads:[~2016-10-31 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-31 19:34 Jim Davis
2016-10-31 20:38 ` Jani Nikula [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=877f8ol0et.fsf@intel.com \
--to=jani.nikula@linux.intel.com \
--cc=corbet@lwn.net \
--cc=jim.epost@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome