On Fri, Apr 23, 2021 at 3:43 PM Luke Shumaker <lukeshu@xxxxxxxxxxx> wrote: > That was nice to have when git-subtree lived out-of-tree. But now that > it lives in git.git, it's not nescessary to keep around. s/nescessary/necessary/ > Signed-off-by: Luke Shumaker <lukeshu@xxxxxxxxxxx> Is there a higher reason for this change aside from "let's do it because we can"? For instance, are subsequent changes going to take advantage of features only present in more recent Git versions which would be painful or impossible to support with the older Git? The downside of this change is that, while git-subtree may live in git.git, it's still just "contrib", so people might grab git-subtree from a modern git.git but then end up using it with an older Git installation. That's not to say that doing such a thing is guaranteed to work anyhow, but we don't need to make it harder on people if there isn't a good reason (hence my question about whether subsequent changes will actually take advantage of newer Git features).
