On Thu, 3 Jan 2008, Sam Vilain wrote: > > Assuming, of course, that the commit you refer to in a message like that > is in your history. If it's referring to another commit in a different > branch, which may be being re-written, you've got two problems: I don't care. If some commit refers to another commit that isn't its ancestor, then that is undefined *anyway*. So the only case that really matters is when you refer to your own strict ancestor. This is one reason why it was so crazy that "git cherry-pick" used to have "-x" by default - appending the original SHA1 (which is generally *not* an ancestor) is meaningless and stupid. But in the case of "git revert", it should be an ancestor (or the _user_ is just insane, in which case it doesn't matter - insane people can do insane things) Linus - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
