Re: Support for a series of patches, i.e. patchset or changeset?

From: Eric Miao <eric.y.miao@gmail.com>
Date: Nov 10, 2012, 09:08 UTC
Message-ID: <CAMPhdO9qNUA=8WG+jTchex3fw=E6spA6pwwJVF+CYJ_orjSaDg@mail.gmail.com>
In-Reply-To: <6df0df49-afb9-4faf-9a2d-6f397f3a167a@zcs>

Yeah, that's a very clean way I'd always want to follow, yet the kernel upstream isn't doing so.

On Sat, Nov 10, 2012 at 4:52 PM, Enrico Weigelt <enrico.weigelt@vnc.biz> wrote:

Show 34 quoted lines

> <snip>
>
> yet another idea:
>
> you coud always put your patchsets into separate branches,
> rebase them ontop target branch before merging, and then
> do an non-ff-merge, which will make the history look like:
>
> * merged origin/feature_foo
> |\
> | * first preparation fo feature foo
> | * part a
> | * part b
> |/
> * merged origin/bugfix_blah
> |\
> | * fixing bug blah
> |/
> *
>
>
> cu
> --
> Mit freundlichen Grüßen / Kind regards
>
> Enrico Weigelt
> VNC - Virtual Network Consult GmbH
> Head Of Development
>
> Pariser Platz 4a, D-10117 Berlin
> Tel.: +49 (30) 3464615-20
> Fax: +49 (30) 3464615-59
>
> enrico.weigelt@vnc.biz; www.vnc.de