Thanks. You're right. I just tried that out. I actually have a deeper problem that I was trying to make a simpler recreation. This wasn't it.
The real problem is, immediately after a clone of a remote bare repo, I run git status and there are several (350) files that are changed and untracked. Of course, since I was running 'git reset' these would not go away, but 'git clean' won't make them go away either. $ git clone ..... $ git status <lots file lines like:> # modified: ........ $ git clean fatal: clean.requireForce not set..... $ git clean -f $ git status <same output as above> On May 16, 4:55 pm, "Peter Harris" <[EMAIL PROTECTED]> wrote: > On Fri, May 16, 2008 at 4:24 PM, John wrote: > > > I've spent a few hours looking for the solution to this. After a > > create a file in a git repo, it is rightly listed in the output of > > 'git status' as 'Untracked'. Then after I run a 'git reset --hard', > > the file is still there in the output. I can even 'git commit -a' and > > the file would be commited, but really, I want to reset --hard. > > > Is there a workaround? > > "git reset" only touches tracked files, not untracked. I think maybe > what you are looking for is "git clean". > > Peter Harris
