3 I spent quite some time cleaning up that patch series, and feel pretty
6 Granted, the new ''git rebase -i -p'' does its job without complaint so far
7 (so much so that I think I'll release a version of my ''rebase'' series
8 soonish), but it _is_ a hassle when you have patches that you have a hard
9 time to decide upon the order/commit boundaries.
11 For example, I could imagine that the patch making the location of the
12 templates independent of the location of the Git binaries should come
13 _before_ my patch series, and the valgrind specific part should then
14 be squashed into the first valgrind commit.
16 Also, it uses two features of valgrind 3.4.0:
19 <li>''...'' in the suppression file, and
20 <li>''--track-origins=yes''
23 The latter is actually the reason I am pretty willing to keep the
24 requirement of that valgrind version, as it is really, really useful.
26 I guess we will see what happens to it.