On May 4, 2010, at 8:29 AM, Jonathan Chetwynd wrote: > ... > > what is the reason permissions are not preserved? > > ... Git implements a network of trust permission model. In this model, system permissions are used (among other things) to control who has access to a repository. Once someone has access, they can perform a clone or a fetch. This process downloads refs into a local repository that inherits your local permissions. This model is simple, but it is often capable of most things that system permissions can do, and it avoids the problem of a given user in the repository not existing on a machine. One of the implications of this model is that although system permissions can be used to control who has access to a repository, they are not stored in the repository itself. This means that if you clone a repository, the system permissions of the repository are never preserved. This is a very intentional detail of the network of trust permission model. Once a user has access to a repository, that user has access to the whole repository. It is exactly like telling another person something. Once the other person hears the data, that person can do whatever he or she wants with it. He or she "owns" a copy of the data. In other words, if you want a user X to own a repository upon cloning, then user X must be the one to perform the clone. If you want Sue to know that the new kitchen table is made of oak, then Sue must be the one to ask the question (aka clone or fetch). You cannot ask the question for Sue and expect her to instantly know what you know. HTH ~ Andrew Keller -- 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