Nix <nix@xxxxxxxxxxxxx> writes: > On 19 Jul 2007, David Kastrup stated: >> Tomash Brechko <tomash.brechko@xxxxxxxxx> writes: >>> Please consider this: I myself use Git to track my own local >>> projects, and for this usage you proposal have no value for me, >>> i.e. as a _Source_ Code Management system Git is rather complete. >>> But I also track /etc and ~/ in Git, and for this I'd love to have >>> directories, permissions, ownership, other attributes, to be >>> tracked. I have Perl script wrapping Git that allows me to filter >>> tracked paths by full regexps instead of Git's file globs, and also >>> to filter out too big files assuming that they are binary anyway. >> >> Look, git _tracks_ contents. Your permissions managements needs to >> be told explicitly when and how things change. So you end up with >> git _tracking_ material and your permissions/directory management >> needing the level of manual handholding Subversion demands. > > Actually, if we had a post-checkout hook, we could use a pre-commit > hook to keep track of directory existence, permissions, et seq, and > a post- checkout hook to restore them. Actually, tracking permissions would be cheap: one just needs to replace the permission-munging macros in git with identity. Ownership -- well, that's harder. But my sentiment remains: git _tracks_ stuff: it notices when things move around and follows them. Statically snapshotting permissions creates a layer that is quite less flexible. The information gets detached. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum - 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
