On Thu, May 01, 2025 at 03:59:56PM -0700, Junio C Hamano wrote: > This does not go far enough to touch the "Git 3.0 removal" list in > Documentation/BreakingChanges.adoc, but is a preparatory step > necessary if we ever wanted to do so in the future. I'm a little confused. These patches very much feel like starting the deprecation process for git-whatchanged(1), so why wouldn't we at the same time list it as an upcoming breaking change? Or is the intent rather to figure out whether anybody is still using this command so that we can then deprecate it after a couple releases if we haven't heard back from anybody? Patrick
