linux-kernel - Re: [GIT PULL] UML changes for 4.20-rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAHk-=wgWy-GwTMQLE1t__fA6Lse8V0J5h4Pkd6mHY7DnZYqFWQ@mail.gmail.com>
Date:   Wed, 31 Oct 2018 16:05:41 -0700
From:   Linus Torvalds <torvalds@...ux-foundation.org>
To:     richard@....at
Cc:     linux-um@...ts.infradead.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [GIT PULL] UML changes for 4.20-rc1

On Wed, Oct 31, 2018 at 4:01 PM Richard Weinberger <richard@....at> wrote:
>
> Okay, so my rebase was in vain, I thought you don't like pull requests
> with such an old base.

Some *really* old bases can cause problems, but generally that's if
it's more than a year old (or if there's been some major upheaval that
happens to particularly strike your particular code).

Honestly, I don't think I can recall any actual "that is based on
something so old that it actually gets problematic" case ever having
happened.  But I could imagine it.

So if it's "a release or two", it's not worth rebasing for. Not unless
there is some other pressing reason (ie some screw-up that requires a
rebase).

                   Linus