From: mchehab@s-opensource.com (Mauro Carvalho Chehab)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Latest kernel documentation tree
Date: Wed, 26 Oct 2016 09:05:35 -0200 [thread overview]
Message-ID: <20161026090535.098f26ae@vento.lan> (raw)
In-Reply-To: <CABEz4DVLM1pB2wHuCWQ=d8TGwnTLWa+MgEDEqHjNwChPm_a3Yg@mail.gmail.com>
Em Wed, 26 Oct 2016 14:25:13 +0530
Jai Krishna <rjk1024@gmail.com> escreveu:
> > 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
>
> Doh! Didnt occur to me to look in MAINTAINERS first.
>
> Thats my lesson for the day!
Jai, let me hijack this thread, to use it as an example :)
Hi Jon,
That's why I think we should add MAINTAINERS somehow at the documentation...
This is not the first time I've seen someone wanting to contribute
but not being able to find the proper maintainer or development tree,
because he's unaware about the contents of MAINTAINERS.
Regards,
Mauro
prev parent reply other threads:[~2016-10-26 11:05 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
2016-10-26 8:55 ` Jai Krishna
2016-10-26 11:05 ` Mauro Carvalho Chehab [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=20161026090535.098f26ae@vento.lan \
--to=mchehab@s-opensource.com \
--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.