Pavel Sanda wrote: > The problem is that such behaviour is intentional i guess, my > understanding is File exists & is in repo -> we load with git support > File exists & not in repo-> ?? porcelain case, we don't load with VCS > support File !exists& we are in repo (more exactly within dir structure > where .git can be found in ancestors) -> we offer to check it out from > archive (your "bug") File !exists& we are not in repo -> just create new > file
This is a feature that did only work for RCS for a long time, and which I extended to the other VCS as well recently: If you try to open a file, and the file does not exist locally, and you are in a tree which is under version control, and the file exists is the repository, you are asked whether you want to retrieve it. The rationale is to prevent users from accidentally creating a new file with a name that does already exist in VCS. If the file is not in VCS, you should not be asked. I believe that this is a useful feature, so the question is: Does it behave like I described in your case? If not, it is a bug and should be fixed. If yes, and the feature is getting in your way, we can also remove it, but for all VCS. I don't see why git should be special here. > Perhaps we can drop this check-out behaviour if it makes troubles, wait > for Georg's opinion. There is also still the problem that we run > GIT::find_file 2x IIRC. Really? I thought I got rid of it. Sorry, I have currently no time to check. Georg
