rethinking patch management with GIT / topgit

[Petr Baudis]

On Wed, Mar 24, 2010 at 01:42:18AM +0100, Enrico Weigelt wrote:
> Once a new upstream is out, somebody simply forks a new branch from
> the last one, rebases it to the new upstream and publishes it when done.
> We actually dont rebase _existing_ (already published) branches, but
> add new ones which just happen to be created via rebase (instead of
> cherry-picking or appling patchsets manually).

But what if you need to change one of the already committed patches?
Suddenly, you lost both (i) and (ii). Sure, you may not consider the
two properties too desirable, but others tend to, especially for
long-term maintenance of large amount of patches by several people
collaboratively.

				Petr "Pasky" Baudis