[Ksummit-discuss] [CORE TOPIC] stable workflow

[Dmitry Torokhov]

On Mon, Jul 11, 2016 at 10:20 AM, Theodore Ts'o <tytso at mit.edu> wrote:
> On Mon, Jul 11, 2016 at 10:15:06AM -0700, Dmitry Torokhov wrote:
>>
>> Cherry picking a commit from a branch/remote is much nicer than fetching
>> a part of [quilt based?] patch queue from git, unless I misunderstand
>> what you are proposing.
>
> The reason why I'm wondering whether or not quilt based might be
> better is because if it turns out that a patch introduces a
> regression, with a quilt based system the patch can be *dropped*, or
> revised in place.
>
> When you do a cherry-pick, you depend on the BSP kernel maintainer
> figuring out that a commit was later reverted, or fixed by a later
> commit that might have a different name, and which doesn't make it
> obvious that if you take commit 'A', you REALLY want to take commits
> 'B' and 'C' as well....

You _never_ use pure stable unless you are talking about bleeding edge
community distro, there is always work on top of stable, so you can't
do "quilt rebases".

-- 
Dmitry