From: Greg KH <greg@kroah.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: is the weeks before -rc1 the time to really be working on -next?
Date: Wed, 15 Oct 2008 10:40:15 -0700 [thread overview]
Message-ID: <20081015174015.GB8663@kroah.com> (raw)
Just wondering, I know that -next is failing right now, and is a major
pain to produce, but that seems to be primarily due to all of the
subsystems merging with Linus right now.
So does it even make sense to try to create a -next during the 2 weeks
of the major merge window? It seems to just cause you a whole lot of
work, that in the end, is mostly unecessary as all of the subsystem
maintainers are doing the merging themselves as trees move into Linus's
tree?
thanks,
greg k-h
next reply other threads:[~2008-10-15 17:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 17:40 Greg KH [this message]
2008-10-15 20:04 ` is the weeks before -rc1 the time to really be working on -next? Geert Uytterhoeven
2008-10-15 20:30 ` Greg KH
2008-10-15 21:56 ` Andrew Morton
2008-10-15 22:08 ` Rafael J. Wysocki
2008-10-15 22:36 ` Alan Cox
2008-10-15 22:53 ` Andrew Morton
2008-10-15 23:08 ` David Miller
2008-10-15 23:41 ` Andrew Morton
2008-10-15 23:53 ` Tony Luck
2008-10-15 23:56 ` David Miller
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=20081015174015.GB8663@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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