linux-kernel - Re: [GIT PULL] LED updates for 4.9-rc6

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: <64a26bd5-1091-34ec-31a0-75c62c471699@gmail.com>
Date:   Sat, 19 Nov 2016 08:40:23 +0100
From:   Jacek Anaszewski <jacek.anaszewski@...il.com>
To:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Jacek Anaszewski <j.anaszewski@...sung.com>
Cc:     Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Linux LED Subsystem <linux-leds@...r.kernel.org>,
        Pavel Machek <pavel@....cz>
Subject: Re: [GIT PULL] LED updates for 4.9-rc6

On 11/18/2016 06:07 PM, Linus Torvalds wrote:
> On Fri, Nov 18, 2016 at 6:13 AM, Jacek Anaszewski
> <j.anaszewski@...sung.com> wrote:
>>
>> Please pull LED subsystem related updates for MAINTAINERS.
>> I'd like to announce a new co-maintainer - Pavel Machek.
>
> No can do.
>
> You've done something incredibly odd, including rebasing my 4.9-rc4
> commit (and four commits before that from other people).

Sorry, I didn't pay enough attention while generating this pull request.

I have the commit to merge also on top of for-next branch.
I copied that branch locally, executed git rebase -i HEAD~20, removed
all preceding commits up to v4.9-rc4 and pushed out. I forgot that git
touches all commits within the range passed to git rebase -i. Certainly
I should have used git rebase --onto, as in my usual workflow.

I've just generated new pull request in the right way.

-- 
Best regards,
Jacek Anaszewski