From: Wolfram Sang <wsa@the-dreams.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Rosin <peda@axentia.se>,
linux-i2c@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PULL REQUEST] i2c for 4.11
Date: Sat, 11 Mar 2017 16:59:20 +0100 [thread overview]
Message-ID: <20170311155919.GA2553@tetsubishi> (raw)
In-Reply-To: <CA+55aFwjUWLFBwyS9iNKA=43tX5Ki+Xu7L_tKMKEa7buVnscBA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 994 bytes --]
Linus,
> You added an extra revert, only to pull in the *exact* same patch. WTF?
The patch I reverted had a broken, typoed Signed-off. My rationale was
to have only a proper one, and not two different ones coming from
different trees. Looks like I misjudged, sorry.
> Please stop this kind of stupidity. Now I have that unnecessary revert
> with a misleading commit log in my tree, in addition to that stupid
> merge that has no explanation and just reinstates the exact same thing
> you reverted.
I see your point.
> And talking about that merge I will repeat this one more time: merges
> are commits too. You had damn well add explanations for what a merge
> merges and why it is done.
Understood. Peter joined as co-maintainer kind of recently, and I guess
it shows that I didn't have to pass on merges a lot so far. It is not
that I ignored your preferences for merges (which make total sense to
me), I just missed to check how to properly do it. Will improve!
Regards,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2017-03-11 16:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 12:33 [PULL REQUEST] i2c for 4.11 Wolfram Sang
2017-03-10 18:12 ` Linus Torvalds
2017-03-11 15:59 ` Wolfram Sang [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-03-31 21:09 Wolfram Sang
2017-02-24 21:50 Wolfram Sang
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=20170311155919.GA2553@tetsubishi \
--to=wsa@the-dreams.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@axentia.se \
--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;
as well as URLs for NNTP newsgroup(s).