public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guenter Roeck <linux@roeck-us.net>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"lm-sensors@lm-sensors.org" <lm-sensors@lm-sensors.org>
Subject: Re: [GIT PULL] hwmon updates for 3.17
Date: Tue, 05 Aug 2014 17:51:11 -0700	[thread overview]
Message-ID: <53E17BFF.70403@roeck-us.net> (raw)
In-Reply-To: <CA+55aFx26rhMq_y0wuBrGi+QhFH0Odtg2eof-r_J6L46opsrjA@mail.gmail.com>

On 08/05/2014 03:58 PM, Linus Torvalds wrote:
> On Mon, Aug 4, 2014 at 8:22 PM, Guenter Roeck <linux@roeck-us.net> wrote:
>>>
>>> This branch was rewritten (but not rebased) to add 5 commits at its
>>> start and 8 commits at its end since yesterday's linux-next.
>>
>> Yes, the start because I missed to send a bunch of fixes to Linus last week
>> because I was on vacation
>> and merged it all together, and the end because I missed to push out a bunch
>> of patches for the same
>> reason. Everything did pass my test suite, though.
>>
>> If that is a problem, let me know.
>
> Please, next time, just send me *two* pull requests - one with the
> missed fixes, and one with the linux-next work. No point in rewriting
> the series so that all the commits are now different from the ones in
> linux-next.
>
Ok, will do.

> I've pulled it, but why rewrite history and mess up the next statistics?
>

Thanks,
Guenter


      reply	other threads:[~2014-08-06  0:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-05  2:22 [GIT PULL] hwmon updates for 3.17 Guenter Roeck
2014-08-05  3:14 ` Stephen Rothwell
2014-08-05  3:22   ` Guenter Roeck
2014-08-05 22:58     ` Linus Torvalds
2014-08-06  0:51       ` Guenter Roeck [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=53E17BFF.70403@roeck-us.net \
    --to=linux@roeck-us.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm-sensors@lm-sensors.org \
    --cc=sfr@canb.auug.org.au \
    --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