You might want to do this in the form of requiring signed-off-by lines. That'd be a relatively easy thing to check for in an update hook; sure, they're a little easier to fake than authorship information, but they permanently record the information.
On Jan 21, 5:14 pm, Jeffda <daniel.viviot...@gmail.com> wrote: > Thanks for the replies/ideas. I think I'll stick with your idea, > Jacob, unless someone has an even more secure solution that's simpler > than creating a wrapper. Creating a wrapper is a good idea, I just > don't know how to, and I don't have time to figure out how to create > one. > > Thanks again. -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To post to this group, send email to git-us...@googlegroups.com. To unsubscribe from this group, send email to git-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/git-users?hl=en.
