From: Roland Dreier <rdreier@cisco.com>
To: Valdis.Kletnieks@vt.edu
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org, Jan Kara <jack@ucw.cz>,
Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: 2.6.26-mmotm-0724 - linux-next.git loses /proc/sys/fs/quota, breaks disk quotas
Date: Sat, 26 Jul 2008 20:50:37 -0700 [thread overview]
Message-ID: <adatzec56k2.fsf@cisco.com> (raw)
In-Reply-To: <21657.1217130229@turing-police.cc.vt.edu> (Valdis Kletnieks's message of "Sat, 26 Jul 2008 23:43:49 -0400")
> I've bisected through Linus' tree more than once - ISTR that there was
> some special funkiness in dealing with trying to bisect through linux-next
> because the tree gets redone every night.
> If it *was* as easy as Linus's tree to bisect, I'd go ahead and do it.
For a single day's linux-next tree, it should be just like Linus's
tree... just clone
git://git.kernel.org/pub/scm/linux/kernel/git/sfr/linux-next.git
and bisect as usual.
The funkiness is that if you say, "linux-next from July 24 worked,
linux-next from July 25 didn't," then it's pretty much hopeless, exactly
because those two trees were built independently.
- R.
next prev parent reply other threads:[~2008-07-27 3:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-27 2:22 2.6.26-mmotm-0724 - linux-next.git loses /proc/sys/fs/quota, breaks disk quotas Valdis.Kletnieks
2008-07-27 3:25 ` Andrew Morton
2008-07-27 3:43 ` Valdis.Kletnieks
2008-07-27 3:50 ` Roland Dreier [this message]
2008-07-27 4:09 ` Al Viro
2008-07-27 5:17 ` [PATCH] " Al Viro
2008-07-27 5:31 ` [PATCH] lost sysctl fix Al Viro
2008-07-27 6:29 ` Ingo Molnar
2008-07-27 6:35 ` Ingo Molnar
2008-07-27 6:31 ` Valdis.Kletnieks
2008-07-27 5:53 ` [PATCH] Re: 2.6.26-mmotm-0724 - linux-next.git loses /proc/sys/fs/quota, breaks disk quotas Valdis.Kletnieks
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=adatzec56k2.fsf@cisco.com \
--to=rdreier@cisco.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=jack@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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.