Matthieu Moy <Matthieu.Moy@xxxxxxx> writes: > Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > >>> > We do not track permissions of directories at all. >>> >>> Ok, this seems like something that should be done as well, even if we >>> can stipulate at first that a directory should have rwx for the user >>> in question if you hope to track it. >> >> No, no, no. It should not be tracked. It is the responsibility of the >> _user_ to set it to something sane, be that by a umask or by sticky >> groups, or by setting the permissions of the parent directory. >> >> It is _nothing_ we want to put into the repository. That is the _wrong_ >> place to put it. > > I'm not sure it's wrong to be able to track permissions, but it's > definitely wrong to track them by default. I am not sure about "definitely", but there certainly are applications where it is appropriate. > * Execute bit. This one is relevant. Indeed, it's more a kind of > metadata than really a permission (you can still execute the file > with /lib/ld-linux.so.2 /path/to/file or such kind of things). Please spare us the sophistry. Probably the most flexible approach would be to be able to specify a checkout umask, defaulting to 700 (the other bits are then filled in from the normal user umask). For archival purposes, one would then set it to 777 instead. There is the question how to deal with checkins. While there is no harm in checking in the full permissions in case one would need them, it would likely be a nuisance to track the individual contributor's settings. -- David Kastrup - 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
