Re: linux-next: please clean up the livepatching tree

On Fri, 5 Aug 2016, Takashi Iwai wrote: > > Exactly to avoid Linus' tree being polluted by the extra merge commits. > > > > My workflow is really simple -- development happens in (a lot of) topic > > branches, and each and every time any of the topic branches is updated by > > a new commit,

Re: linux-next: please clean up the livepatching tree

On Fri, 5 Aug 2016, Takashi Iwai wrote: > > Exactly to avoid Linus' tree being polluted by the extra merge commits. > > > > My workflow is really simple -- development happens in (a lot of) topic > > branches, and each and every time any of the topic branches is updated by > > a new commit,

Re: linux-next: please clean up the livepatching tree

On Wed, 03 Aug 2016 11:29:02 +0200, Jiri Kosina wrote: > > On Wed, 3 Aug 2016, Stephen Rothwell wrote: > > > > This is a part we keep discussing from time to time, and I still don't > > > understand why it bothers you so much. The only reason is to keep the > > > branch non-rebasing, because

Re: linux-next: please clean up the livepatching tree

On Wed, 03 Aug 2016 11:29:02 +0200, Jiri Kosina wrote: > > On Wed, 3 Aug 2016, Stephen Rothwell wrote: > > > > This is a part we keep discussing from time to time, and I still don't > > > understand why it bothers you so much. The only reason is to keep the > > > branch non-rebasing, because

Re: linux-next: please clean up the livepatching tree

On Wed, 3 Aug 2016, Stephen Rothwell wrote: > > This is a part we keep discussing from time to time, and I still don't > > understand why it bothers you so much. The only reason is to keep the > > branch non-rebasing, because it has downstreams. Code-wise, it's > > always equivalent to what

Re: linux-next: please clean up the livepatching tree

On Wed, 3 Aug 2016, Stephen Rothwell wrote: > > This is a part we keep discussing from time to time, and I still don't > > understand why it bothers you so much. The only reason is to keep the > > branch non-rebasing, because it has downstreams. Code-wise, it's > > always equivalent to what

Re: linux-next: please clean up the livepatching tree

Hi Jiri, On Wed, 3 Aug 2016 01:41:17 +0200 (CEST) Jiri Kosina wrote: > > On Wed, 3 Aug 2016, Stephen Rothwell wrote: > > > The livepatching tree > > (git://git.kernel.org/pub/scm/linux/kernel/git/jikos/livepatching#for-next) > > today consists of only lots of merges > >

Re: linux-next: please clean up the livepatching tree

Hi Jiri, On Wed, 3 Aug 2016 01:41:17 +0200 (CEST) Jiri Kosina wrote: > > On Wed, 3 Aug 2016, Stephen Rothwell wrote: > > > The livepatching tree > > (git://git.kernel.org/pub/scm/linux/kernel/git/jikos/livepatching#for-next) > > today consists of only lots of merges > > This is a part we

Re: linux-next: please clean up the livepatching tree

Hi Stephen On Wed, 3 Aug 2016, Stephen Rothwell wrote: > The livepatching tree > (git://git.kernel.org/pub/scm/linux/kernel/git/jikos/livepatching#for-next) > today consists of only lots of merges This is a part we keep discussing from time to time, and I still don't understand why it bothers

Re: linux-next: please clean up the livepatching tree

Hi Stephen On Wed, 3 Aug 2016, Stephen Rothwell wrote: > The livepatching tree > (git://git.kernel.org/pub/scm/linux/kernel/git/jikos/livepatching#for-next) > today consists of only lots of merges This is a part we keep discussing from time to time, and I still don't understand why it bothers

linux-next: please clean up the livepatching tree

Hi Jiri, The livepatching tree (git://git.kernel.org/pub/scm/linux/kernel/git/jikos/livepatching#for-next) today consists of only lots of merges (and a patch that is also reverted). Please just reset it to somewhere in Linus' tree. -- Cheers, Stephen Rothwell

linux-next: please clean up the livepatching tree

Hi Jiri, The livepatching tree (git://git.kernel.org/pub/scm/linux/kernel/git/jikos/livepatching#for-next) today consists of only lots of merges (and a patch that is also reverted). Please just reset it to somewhere in Linus' tree. -- Cheers, Stephen Rothwell