Hi, On mardi 10 novembre 2009, Michael J Gruber wrote: > Hi there, > > when cooking up a "warning example" for git replace (don't draw > premature conclusions when there are replaced objects) I came across the > following problem: git status seems to compare the work dir with the > tree of HEAD, not the replacing tree. Even deleting the index does not > help. Yeah, you are right. I must say that I never tested replacing trees before. > [ The example also shows that we need a way to specify > --no-replace-objects for gitk. Would easier if gitk really where git > something. ] Yeah, I think --no-replace-objects might not work well for shell scripts or even commands that call other commands using run_command(). Perhaps we need an environment variable GIT_NO_REPLACE_OBJECTS to be set by commands that are passed --no-replace-objects and checked by all the commands. I will have a look at that. Thanks, Christian. -- 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