Rémi Vanicat <[email protected]> writes: > After testing, it seem that the simper is to go on the first unpushed > commit, do r b, then go down in history: the default value appear. You > just have to add ~1 to have the one you want.
Unfortunately that trick works only with the builtin completer. PJ Weisberg <[email protected]> writes: > On Tuesday, May 3, 2011, Hannu Koivisto <[email protected]> wrote: >> [1] In fact, even before this change rewriting is not as convenient >> as it could be and I'm contemplating features such as amending ... > Careful you don't make it *too* convenient. Some of those are the > sort of thing that you *shouldn't* do to a history that other people > base their branches on, for reasons that aren't obvious to people > switching over from other version control systems. Perhaps such features could be limited to unpushed commits by default (not that Magit's idea of unpushed guarantees anything) or put completely behind some "I know what I'm doing, damnit!"-flag akin to Emacs' disabled commands feature but that's a policy question I'm not that interested in. One could also ask if Magit's other destructive commands should be treated the same way. In any case I just want easier ways to do some of the things that I already do with Magit's rewrite feature. Btw, don't get me wrong; Magit's rewrite feature is already immensely convenient compared to using git's interactive rebase. It's definitely in top 2 killer features of Magit for me. -- Hannu
