From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux LED Subsystem <linux-leds@vger.kernel.org>,
amitoj1606@gmail.com, ao2@ao2.it, drivshin@allworx.com,
Geert Uytterhoeven <geert+renesas@glider.be>,
hkallweit1@gmail.com, stefan.wahren@i2se.com,
Wei Yongjun <yongjun_wei@trendmicro.com.cn>
Subject: Re: [GIT PULL] LED subsystem updates for 4.6
Date: Wed, 16 Mar 2016 08:40:47 +0100 [thread overview]
Message-ID: <56E90DFF.6090603@samsung.com> (raw)
In-Reply-To: <CA+55aFz5YTwNHH9M3UuJ70_S8R6bbmPOqb8CA2soeGPaJ+i5ZQ@mail.gmail.com>
On 03/16/2016 06:04 AM, Linus Torvalds wrote:
> On Tue, Mar 15, 2016 at 12:51 AM, Jacek Anaszewski
> <j.anaszewski@samsung.com> wrote:
>>
>> I just wanted to make sure that no unexpected problem has occurred
>> after rebasing onto 4.5 release. Is it in some way more advantageous to
>> base a pull request on rc7, than on a final release?
>
> I'd rather see the pull request based on whatever it has been tested
> on, and just keep it that way.
>
> Any rebasing will inevitably mean that you are basically throwing all
> previous testing out the window (or at least make it dubious).
>
> Rebasing also makes it much harder to see the history (for example,
> compare it against previous linux-next trees), so the rule really
> should be that you should never rebase unless you have a major reason
> to do so.
>
> So for example, if you actually find a problem, and you notice that
> that problem comes not from your own changes, but from the base you
> picked - *then* you'd want to rebase to a more stable base. But a
> rebase "just because" is not a good idea.
>
> I'll pull it, since it looks fairly harmless, but basically please
> don't do that again.
Thanks for the explanation. I'll proceed accordingly.
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2016-03-16 7:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 10:24 [GIT PULL] LED subsystem updates for 4.6 Jacek Anaszewski
2016-03-14 23:36 ` Stephen Rothwell
2016-03-15 7:51 ` Jacek Anaszewski
2016-03-16 5:04 ` Linus Torvalds
2016-03-16 7:40 ` Jacek Anaszewski [this message]
2016-03-16 5:15 ` Linus Torvalds
2016-03-16 7:47 ` Jacek Anaszewski
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=56E90DFF.6090603@samsung.com \
--to=j.anaszewski@samsung.com \
--cc=amitoj1606@gmail.com \
--cc=ao2@ao2.it \
--cc=drivshin@allworx.com \
--cc=geert+renesas@glider.be \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=stefan.wahren@i2se.com \
--cc=torvalds@linux-foundation.org \
--cc=yongjun_wei@trendmicro.com.cn \
/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