* Eli Schwartz <[email protected]> [2015-06-11 23:37:25 -0500]: > On Thu, Jun 11, 2015 at 11:24 PM, Florian Bruhin <[email protected]> > wrote: > > > Hmm. Instinctively I'd have agreed, but I can't reproduce this. > > > > I think git filter-branch actually checks out each "vanilla" commit > > from the original branch to apply the given changes, and doesn't base > > them on the already-changed commits: > > > > [...] > > > > Am I missing something? Have you actually verified this or is it just > > a guess? ;) > > > > [...] > > Either way, is it that terrible to make sure the .SRCINFO is up to date? If > there is already one, it *should* just replace it with an identical copy... > resulting in no diff. And if there is a diff, that means something once > went wrong...
No, of course the change *does* make sense. Sorry for not making this more clear in my answer. I was mainly trying to figure out if I have to find out how I could force-push to correct anything that's been pushed wrong, and then found out it's hopefully not necessary to do so. Florian -- http://www.the-compiler.org | [email protected] (Mail/XMPP) GPG: 916E B0C8 FD55 A072 | http://the-compiler.org/pubkey.asc I love long mails! | http://email.is-not-s.ms/
pgpqKGrTVjvkJ.pgp
Description: PGP signature
