On Thu, May 23, 2013 at 7:20 PM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Thomas Rast <trast@xxxxxxxxxxx> writes: > >>> What are the workflows that are helped if we had such a bit? If >>> we need to support them, I think you need a real --ignore-changes >>> bit, not an abuse of --assume-unchanged. >> >> I gather -- from #git -- that it's mostly used for config files, which >> have an annoying habit of being different from the repository. >> >> Which is wrong, really. But we still claim that --assume-unchanged is a >> solution to it in git-update-index(1). > > That is doubly wrong, then ;-) > > How would we want to proceed from here? The obvious first step > would be to fix the documentation, but then what is next? > > Thinking aloud, ignoring that "Which is wrong, really" part in your > message and assuming that we do want to support --ignore-changes.... The wording of --ignore-changes suffers the same lack of clarity that --assume-unchanged does. --assume-unchanged : These changes are ephemeral --ignore-changes : These changes are precious but not to be committed What's better? --sequester is probably too obscure. Maybe --hold. Or --silence. Or --shut-up. Does this mean a new class of files for git-status? Added, changed, untracked, ignored and held? I wonder if there is a use case for such a switch to be applied to content rather than files. Suppose I want to --hold these changes, but further changes to the same files should be fair game? That's probably an insane situation for some future itch and not this one. Anyway, it sounds like it would involve the index or maybe a 2nd index. Phil -- 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