All of lore.kernel.org
 help / color / mirror / Atom feed
From: gregkh@linuxfoundation.org (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Latest kernel documentation tree
Date: Wed, 26 Oct 2016 10:33:54 +0200	[thread overview]
Message-ID: <20161026083354.GA11680@kroah.com> (raw)
In-Reply-To: <CABEz4DUR891G5L1NbDap7FmD4N_g3AkTg853sOLw1M1M9JWz0Q@mail.gmail.com>

On Wed, Oct 26, 2016 at 01:33:34PM +0530, Jai Krishna wrote:
> Hello,
> 
> Im trying to follow the documentation work of converting to Sphinx etc
> that Jon, Mauro and others are doing ( inferring from the patches
> coming into kernel-docs@ ).
> 
> Id like to be able to pull and build the Sphinx based docs, learn and
> possibly even contribute (wish, wish...). However, Im stuck on a very
> mundane thing. Im not quite sure which tree has the latest sources.
> 
> I looked at kernel/kernel-docs.git on git.kernel.org but that seems
> stale. Im not quite sure if its kernel/gregkh/staging.git.
> 
> Can someone kindly point me to the correct tree that has the latest
> sources of Sphinx docs?

Don't worry, it's not the staging.git tree, that has nothing to do with
the documentation tree :)

Have you looked at MAINTAINERS?  It shows that:
	T:      git git://git.lwn.net/linux.git docs-next
is the tree to look at.  Have you tried that?

thanks,

greg k-h

  parent reply	other threads:[~2016-10-26  8:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-26  8:03 Latest kernel documentation tree Jai Krishna
2016-10-26  8:29 ` Mauro Carvalho Chehab
2016-10-26  8:33 ` Greg KH [this message]
2016-10-26  8:55   ` Jai Krishna
2016-10-26 11:05     ` Mauro Carvalho Chehab

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=20161026083354.GA11680@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=kernelnewbies@lists.kernelnewbies.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 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.