david@xxxxxxx writes: > my initial thoughts were to have git do all it's normal work and hook > into git at the point where it's writing the file out (where today it > chooses between writing the data to a file on disk, pipeing to stdout, > or pipeing to a pager) by adding the option to pipe into a different > program that would deal with the permission stuff. this program would > only have to write the file and set the permissions, it wouldn't have > to know anything about git other then where to find the permissions it > needs to know. > > it sounds like you are suggesting that the hook be much earlier in the > process,... Well, you misread me or what I said was confusing or both. I was suggesting totally opposite. Let git do all its normal work, and then call your hook to munge the work tree in any way you want. - 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
