On Thu, 7 May 2009, Linus Torvalds wrote:
On Thu, 7 May 2009, david@xxxxxxx wrote:
even with this a git checkout -f should replace all files, correct?
Hmm. I don't think so.
As far as I recall, "-f" only overrides certain errors (like unmerged
files or not up-to-date content), it doesn't change behavior wrt files
that git thinks are already up-to-date.
what about a reset --hard? (is there any command that would force the
files to be re-written, no matter what git thinks is already there)
David Lang
--
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