From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Jacek Anaszewski <j.anaszewski@samsung.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux LED Subsystem <linux-leds@vger.kernel.org>,
Pavel Machek <pavel@ucw.cz>
Subject: Re: [GIT PULL] LED updates for 4.9-rc6
Date: Sat, 19 Nov 2016 08:40:23 +0100 [thread overview]
Message-ID: <64a26bd5-1091-34ec-31a0-75c62c471699@gmail.com> (raw)
In-Reply-To: <CA+55aFwH1Bxne+CNBLucq-26E__juV7iUJhedc=UKEDTgaiopw@mail.gmail.com>
On 11/18/2016 06:07 PM, Linus Torvalds wrote:
> On Fri, Nov 18, 2016 at 6:13 AM, Jacek Anaszewski
> <j.anaszewski@samsung.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
prev parent reply other threads:[~2016-11-19 7:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-18 14:13 Jacek Anaszewski
2016-11-18 17:07 ` Linus Torvalds
2016-11-19 7:40 ` Jacek Anaszewski [this message]
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=64a26bd5-1091-34ec-31a0-75c62c471699@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=j.anaszewski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@ucw.cz \
--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®