From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: kernel-janitors@vger.kernel.org
Subject: Re: [staging:staging-next 70/73] drivers/staging/comedi/drivers/amplc_dio200.c:1444:2: error: implic
Date: Wed, 15 Aug 2012 14:47:01 +0000 [thread overview]
Message-ID: <20120815144701.GA6320@kroah.com> (raw)
In-Reply-To: <502B71C7.4010005@mev.co.uk>
On Wed, Aug 15, 2012 at 10:35:05PM +0800, Fengguang Wu wrote:
> > Wait, what do you mean by "non-rebaseable"? I think you mean
> > "non-bisectable" right?
>
> I mean, the branch will not be rebased to fixup errors in the middle.
> Like the Linus' tree, and the tip/net trees. For these branches that
> cannot afford to rebase, bug fixes always get appended rather than get
> folded into the buggy commit.
>
> For the non-rebaseable branches, I'll first build test the branch HEAD,
> and iff it has build errors, go back to locate the first commit that
> introduces the errors. This way, it can avoid sending out pointless
> warnings about known bugs that are eventually fixed up in the HEAD.
None of my trees and branches should ever be rebased, unless something
really wrong goes on. I think I've only had to ever do this once, for
one branch, in the past years that I've been doing this.
greg k-h
next prev parent reply other threads:[~2012-08-15 14:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 9:54 [staging:staging-next 70/73] drivers/staging/comedi/drivers/amplc_dio200.c:1444:2: error: implic Ian Abbott
2012-08-15 13:54 ` Greg Kroah-Hartman
2012-08-15 14:07 ` Fengguang Wu
2012-08-15 14:10 ` Greg Kroah-Hartman
2012-08-15 14:35 ` Fengguang Wu
2012-08-15 14:47 ` Greg Kroah-Hartman [this message]
2012-08-15 14:50 ` Fengguang Wu
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=20120815144701.GA6320@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=kernel-janitors@vger.kernel.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.