Eric Wong <e@xxxxxxxxx> writes: [...] > AFAIK, filter-branch is not causing support headaches for any > git developers today. With so many commands in git, it's > unlikely newbies will ever get around to discover it :) > So I think think we should be in any rush to remove it. Nah, discovering it is simple. Just Google for "git change author". That eventually leads to a script that uses "git filter-branch --env-filter" to get the job done, and I'm afraid it is spread all over the world. See, e.g.: https://help.github.com/en/articles/changing-author-info > But I agree that filter-branch isn't useful and certainly > shouldn't be encouraged/promoted. Well, is there more suitable way to change author for a (large) set of commits then? > Yet there's probably still users which ARE happy with it, that > will never hit the edge cases and problems it poses; and will > never read release notes. And said users are probably getting > git from a slow-moving distro, so it'd be a disservice to them > if they lost a tool they depend on without any warning. Personally, I'm far from happy with it, but I have no clue how to substitute it in the job above. Anybody? -- Sergey
