From: Rene Herman <rene.herman@keyaccess.nl>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: David Brownell <david-b@pacbell.net>,
Michael Buesch <mb@bu3sch.de>,
sfr@canb.auug.org.au, linux-kernel@vger.kernel.org,
Greg KH <greg@kroah.com>
Subject: Re: [PATCH] gpiolib: Allow user-selection
Date: Thu, 03 Jul 2008 10:36:44 +0200 [thread overview]
Message-ID: <486C8F9C.7080507@keyaccess.nl> (raw)
In-Reply-To: <20080702220842.44364045.akpm@linux-foundation.org>
On 03-07-08 07:08, Andrew Morton wrote:
> But what I am repeatedly seeing is people cheerfully raising 2.6.27
> patches against the 2.6.26 tree when we have a nice 2.6.27 tree for
> developing against. Those days are over, guys.
>
> I'm also seeing obvious signs that developers aren't _testing_ their
> new code within the context of the 2.6.27 tree. They're obviously
> testing their stuff against 2.6.26 and then hoping and praying, only
> it doesn't always work out for them.
Developing against -next is even worse than developping against an -rc1.
You normally want to be running the code you develop meaning you'd very
frequently drown in everyone else's bugs without getting to your own if
you do. Development needs to happen against something relatively stable
really and the last release would generally seem to be the best choice.
Now ofcourse, _porting_ it to -next before submitting makes lots of
sense but positioning -next as THE devel tree a bit less I feel...
Rene.
next prev parent reply other threads:[~2008-07-03 12:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-02 21:46 [PATCH] gpiolib: Allow user-selection Michael Buesch
2008-07-03 0:04 ` Andrew Morton
2008-07-03 0:26 ` Michael Buesch
2008-07-03 5:00 ` David Brownell
2008-07-03 5:08 ` Andrew Morton
2008-07-03 5:41 ` David Brownell
2008-07-03 19:37 ` Greg KH
2008-07-03 21:28 ` David Brownell
2008-07-03 23:08 ` Greg KH
2008-07-12 5:32 ` David Brownell
2008-07-03 8:36 ` Rene Herman [this message]
2008-07-03 9:01 ` Andrew Morton
2008-07-03 10:19 ` Rene Herman
2008-07-03 8:25 ` David Brownell
2008-07-03 8:42 ` Michael Buesch
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=486C8F9C.7080507@keyaccess.nl \
--to=rene.herman@keyaccess.nl \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=sfr@canb.auug.org.au \
/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