Junio C Hamano, Sun, Apr 23, 2006 02:54:51 +0200: > Alex Riesen <raa.lkml@gmail.com> writes: > > > I had a project where lots of files were "accidentally" marked +x, and > > doing plain "git-update-index --chmod=-x" for each file was too slow. > > Besides, it's somewhat inconsistent, that --chmod does work only for > > one subsequent file. > > If you are doing that on the command line, people may want to > have a way to mean "from here on do not do chmod, just do normal > update-index and nothing else" by resetting the chmod_mode thing > back to zero. Nothing major, and we do not do that to allow_add > and allow_remove either, but just a thought. I am unsure about this. I'm even attaching instead of inlining the patches, to make it clear how unsure I am :) I have a feeling that it's more understandable to just use two separate commands. Besides, the reset switch makes it impossible to use pathname disambiguation ("--"). Unsure...Received on Sun Apr 23 17:09:28 2006
This archive was generated by hypermail 2.1.8 : 2006-04-23 17:09:46 EST