[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20181015073339.GB981@kunai>
Date: Mon, 15 Oct 2018 09:33:40 +0200
From: Wolfram Sang <wsa@...-dreams.de>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>
Cc: linux-mmc <linux-mmc@...r.kernel.org>,
Ulf Hansson <ulf.hansson@...aro.org>,
Wolfram Sang <wsa+renesas@...g-engineering.com>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 0/2] mmc: uniphier-sd: two bug-fixes
> Some sub-systems rebase, and some do not.
> It is up to the sub-system maintainer.
We used to have a very strict rule to not rebase anything which ends up
in linux-next. Dunno what happened to this rule but I liked it.
> I know what you are saying, but this is how we develop in linux-next.
I wonder about that...
> You need to use "git rebase --onto".
And what about lists with commit IDs tracking patches on their way
upstream? Yes, there is git-patch-id, yet I think it is easier to admit
that incremental changes happen anyway. I know Ulf view differs...
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists