Marcin Bachry <[email protected]> writes: > The attached patch should fix replace-regexp-in-string bug,
Thanks, applied! (I really need to get around adding support for "git am" to Magit...) > but I still have a backtrace when rewriting from the very first > commit. The second patch tries to address this problem, but I'm not > sure it's the correct way: maybe it's more suitable to just throw an > error when someone wants to rewrite the initial commit? Yeah, I think that is best. Your patch would silently start rewriting from the second commit, which is probably just confusing. I've modified it to signal an error. Thanks!
