1 Problems with split-topic-branches.sh
3 So my little script that should help me to split my topic branches does
6 First some background: the idea was to let ''git blame'' do the hard work
7 to find overlapping changes, i.e. changes that would conflict when
8 changing the order (or skipping the first change, on which the next builds).
10 The first problem with that approach: when lines are _removed_ by one
11 commit, and the next commit touches the same location, ''git blame'' does
12 not find that the first commit is required by the second.
14 Therefore I introduced a really slow reverse thing which tries to find
15 those commits whose removals survived until the parent of a particular
16 commit, but not further.
18 However, it does not work properly. Basically, only context sizes that
19 span the whole files lead to conflict-free topic branches so far.
21 As a consequence, I think I'll add an option --sprout to the revision
22 walker which will fake octopus merges (or a series of two-parent merges)
23 whenever it finds a perl of non-merge commits that are theoretically
24 independent, i.e. whose patches apply cleanly.