On Friday 2007 August 03, Rogan Dawes wrote: > > The only method I've found is to delete the file in the work tree then do > > git-checkout again. Even with -f, if the file is not changed git doesn't > > perform a checkout again, so git-checkout -f is not sufficient. I assume > > I can do what I want with some clever plumbing, but I don't know any > > plumbing. :-) > > $ git reset --hard I think that that suffers the same as "git-checkout -f"; if it doesn't see changes then it doesn't reread. Also, it's not possible to do per-file: $ git reset --hard HEAD somefile.txt Cannot do partial --hard reset. Which is a necessity really; I don't want to accidentally overwrite work that's not yet checked in in the rest of the tree. Is git-checkout-index the thing I'm looking for? I'm wondering if the "-n" switch is the trick? Andy -- Dr Andy Parkins, M Eng (hons), MIET andyparkins@xxxxxxxxx - 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
