David Kastrup <dak@xxxxxxx> writes: > I don't even think it prudent to _offer_ the --show-touched option > in a porcelain such as git-diff as long as purportedly read-only > porcelain commands like git-status can trash the state: what is > reported is not actually "touched" but something internal to the > operation of git. > > At least not without a notice in the manual that this option might > or might not work, depending on what one did previously. Proposal: if this option is to stay, call it rather --show-stale since that corresponds better with what the option actually does: show whether git's inode cache went stale. It does _not_ show whether the file has been touched (git-status does not touch files, for example). -- David Kastrup - 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
