another somewhat obscure Git question: if you've ever passed a <tree-ish> to a Git command that was not a commit, but instead some other tree, what were you doing?

I'm trying to come up with some kind of rationale for Git using <tree-ish> instead of <commit> in its documentation (other than the obvious "that's how the software works"), but it's hard for me to understand the use case

Follow

@b0rk I was merging a subtree of another repository into a different path on the destination.

This is the commit in question: gitlab.winehq.org/mono/mono/-/

Sign in to participate in the conversation
Computer Fairies

Computer Fairies is a Mastodon instance that aims to be as queer, friendly and furry as possible. We welcome all kinds of computer fairies!