Geoff Russell <geoffrey.russell@xxxxxxxxx> writes: > On 5/6/09, Thomas Rast <trast@xxxxxxxxxxxxxxx> wrote: > > Geoff Russell wrote: > > > Bug or feature? I don't know. > > > > > > Feature. [...] > Ok, its clearly a policy choice. But suppose I have an untracked > file and I do "git some-command" then I don't expect git to touch what > it doesn't know about. I.e., "git add x" shouldn't delete the untracked > file y. That seems sensible. But now "git checkout branch" behaves > quite differently in just deleting stuff that it doesn't own (i.e., is > untracked). > > Anyway, I'll rethink. First, did you consider just .gitignore'ing untracked files, and if they are compilation products use cc-cache instead? Second, the way git treats untracked files is simple: do not lose information. If a file is tracked, or to be more exact specific contents of a file is in repository, then deleting it would not remove information. -- Jakub Narebski Poland ShadeHawk on #git -- 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