Re: [PATCH 0/6] pre-processing pipeline and transient package replacement

[Baurzhan Ismagulov <ibr@radix50.net>]

On Wed, Apr 24, 2019 at 10:38:08AM +0200, Claudius Heine wrote:
> Well there are different kind of patchsets, some patchsets implement
> features and some just cleanup/refactor code. The latter ones might contain
> a number of small improvements all over the code base. They are related in a
> sense that they 'do' the same (refactoring/cleanup), not necessarily with
> the same code pieces. But they might work towards cleaning
> up/refactoring/preparing the code for a bigger feature or rework that comes
> later.
> 
> So what you are saying that you would prefer instead of putting all those
> small refactoring changes together in one bigger patchset, that I should
> submit all those patches separate from each other? An then state that the
> feature/rework patchset depends on all of them?
> 
> I think that will cause more work on every ones end (especially with the
> slow CI build), but if that is what needs to be done when contributing to
> Isar, I will look into reordering my patchsets accordingly and maybe write
> some scripts to automate this pipeline for myself.

The current practice resulted from past discussions, in which amending patches
without reviewing again or applying series in part had been objected to. I
haven't looked at the proposals in detail yet, but in general, if we can
improve the process to save overall effort, I'm for it.

With kind regards,
Baurzhan.