Stephen R. van den Berg schrieb: > Actually, ripple-through changes are rare. In the current project it > seems I need exactly one, but it's buried deep in the past (sadly). > The reason why I need it, is to make sure that git-bisect will work for > any revision in the past (i.e. the tree contained/contains some > too-clever-for-their-own-good $Revision$-expansion dependencies) But you do know that you don't need to apply the change *now*; you can apply it at bisect-time? Unless you expect you or your mere mortal coworkers are going to do dozens of bisects into that part of the history, I wouldn't change history *like*this*. But of course, I don't understand the circumstances enough, so... just my 2 cents. -- Hannes -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
