From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Richard Weinberger <richard@nod.at>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux-Arch <linux-arch@vger.kernel.org>
Subject: Re: [GIT PULL] Global signal cleanup
Date: Fri, 8 Aug 2014 13:21:35 +1000 [thread overview]
Message-ID: <20140808132135.47e16442@canb.auug.org.au> (raw)
In-Reply-To: <CA+55aFy0OFQ5ncwHwpah4xwxuOuMEWL+w6Dv-akTFnogpLo1yA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1868 bytes --]
Hi all,
On Thu, 7 Aug 2014 08:53:56 -1000 Linus Torvalds <torvalds@linux-foundation.org> wrote:
>
> On Wed, Aug 6, 2014 at 9:35 PM, Richard Weinberger <richard@nod.at> wrote:
> >
> > It would be nice to see these rules written down somewhere.
>
> The rules have been pretty clear: "don't rebase public trees".
>
> That's always been the basic rule. There are _exceptions_ when
> rebasing is the right thing to do, and they all boil down to "lesser
> of two evils", but the evils really have to be pretty big.
>
> Possible reasons to rebase:
>
> (a) It's not public yet. You haven't pushed to kernel.org or any
> other public site, and nobody saw you do it.
So this would not be in linux-next, so I don't care :-)
> (b) You *really* screwed up, and the downsides of rebasing are
> smaller than the downsides of exposing it.
>
> As in "oops, that half-way commit doesn't even compile or work at
> all, so leaving it in that state will screw up anybody trying to find
> other bugs with 'git bisect'"
>
> At the same time, if you do this just before pushing to me, maybe
> you should take a step back and say "oops, my tree was completely
> broken, maybe I shouldn't push this to Linus just after fixing it".
And this is fine but shouldn't happen just before sending a pull
request (as Linus said). But may also require informing anyone who
depends on your tree (especially if that other tree is also in
linux-next ... otherwise I could easily end up with both versions).
> (c) You want to clean things up, and you're not even remotely ready
> to push things upstream, and while people have *seen* your work,
> nobody relies on it or uses it.
And this should not be in linux-next yet, so again I don't care and
shouldn't see it.
--
Cheers,
Stephen Rothwell sfr@canb.auug.org.au
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-08-08 3:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-06 11:18 Richard Weinberger
2014-08-06 11:27 ` Stephen Rothwell
2014-08-06 11:29 ` Richard Weinberger
2014-08-07 0:28 ` Stephen Rothwell
2014-08-07 7:35 ` Richard Weinberger
2014-08-07 18:53 ` Linus Torvalds
2014-08-07 20:47 ` Richard Weinberger
2014-08-07 22:05 ` Richard Weinberger
2014-08-08 3:21 ` Stephen Rothwell [this message]
2014-08-07 20:44 ` Vineet Gupta
2014-08-09 9:17 ` Richard Weinberger
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=20140808132135.47e16442@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®