On 4/13/07, Alex Riesen <raa.lkml@xxxxxxxxx> wrote:
> + * (NOTE! This is old and arguably fairly strange behaviour. > + * We might want to make this an error unconditionally, and > + * use "--force-remove" if you actually want to force removal). ... > + /* Should this be an unconditional error? */ > + return remove_one_path(path); Makes me uncomfortable too. Is it be possible anyone is depending on it? Maybe it still can be changed?
Maybe not. It actually makes sense: the old file (now a directory) is actually removed, so a plain --remove in its old meaning still _is_ correct: remove the file from index if it is removed from working directory. And it breaks t1001. - 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