From 0b156468edac8e0b146f23c98a0d2366d20d5df2 Mon Sep 17 00:00:00 2001 From: "https://www.google.com/accounts/o8/id?id=AItOawmnrN9a3uAu6Ur2SSyE_AiKw7bOon1yJBc" Date: Mon, 30 Jul 2012 23:58:45 +0000 Subject: [PATCH] --- doc/forum/Wishlist:_Don__39__t_make_files_readonly.mdwn | 3 +++ 1 file changed, 3 insertions(+) create mode 100644 doc/forum/Wishlist:_Don__39__t_make_files_readonly.mdwn diff --git a/doc/forum/Wishlist:_Don__39__t_make_files_readonly.mdwn b/doc/forum/Wishlist:_Don__39__t_make_files_readonly.mdwn new file mode 100644 index 0000000000..4d67f93b1a --- /dev/null +++ b/doc/forum/Wishlist:_Don__39__t_make_files_readonly.mdwn @@ -0,0 +1,3 @@ +Maybe this explained somewhere else, but what is the purpose of marking files readonly. To me this is an annoyance that doesn't make sense. I want to be able to change my files, having to go through an unlock step, to do that seems like unnecessary work. Interestingly, Microsoft's Team Foundation Server source control does the same thing and I don't like it there either. + +In addition why replace files with symlinks? Why not just leave the real files in place, or do the reverse and put the symlink to the file in the repository.