From: Sam Ravnborg <sam@ravnborg.org>
To: petkovbb@gmail.com
Cc: Randy Dunlap <rdunlap@xenotime.net>,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH 1/5] docsrc: build Documentation/ sources
Date: Wed, 30 Jul 2008 13:21:36 +0200 [thread overview]
Message-ID: <20080730112136.GA19465@uranus.ravnborg.org> (raw)
In-Reply-To: <9ea470500807300155t60732956m67d196f87aed9fa4@mail.gmail.com>
> >
> > With the current approach we have much better build coverage.
> > All "allyesconfig" and "allmodconfig" builds will do the test
> > builds which is a good think.
> > If we introduce "make docsrc" then almost only Randy will do the
> > test builds and report the breakage - which is not good.
>
> Well, i don't see anymore people than Randy doing
>
> CONFIG_BUILD_DOCSRC=1 make ...
One such example is:
http://kisskb.ellerman.id.au/linux-next
Here the all*config will do the build test of the
documentation and Stephen will tell if it breaks.
> either so only the other option remains, which means CONFIG_BUILD_DOCSRC
> should be "default y" for more coverage...
No - we do not want to set config options to "default y" unless
there are _very_ good reasons to do so.
You should check a few of Linus' responses during
this merge window if you want more background on this.
Sam
next prev parent reply other threads:[~2008-07-30 11:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 20:05 [PATCH 1/5] docsrc: build Documentation/ sources Randy Dunlap
2008-07-29 20:05 ` [PATCH 2/5] docsrc: fix procfs example Randy Dunlap
2008-07-29 20:05 ` [PATCH 5/5] docsrc: fix getdelays printk formats Randy Dunlap
2008-07-29 20:05 ` [PATCH 4/5] docsrc: fix crc32hash type Randy Dunlap
2008-07-30 6:47 ` Dominik Brodowski
2008-07-30 7:18 ` Andrew Morton
2008-07-30 8:40 ` Sam Ravnborg
2008-07-29 20:05 ` [PATCH 3/5] docsrc: fix ifenslave type Randy Dunlap
2008-07-29 20:27 ` [PATCH 1/5] docsrc: build Documentation/ sources Borislav Petkov
2008-07-29 21:10 ` Randy Dunlap
2008-07-30 8:44 ` Sam Ravnborg
2008-07-30 8:55 ` Boris Petkov
2008-07-30 11:21 ` Sam Ravnborg [this message]
2008-07-30 12:22 ` Boris Petkov
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=20080730112136.GA19465@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petkovbb@gmail.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