On Wed, Apr 15, 2009 at 12:20:54PM -0700, Shawn O. Pearce wrote: > > Not sure of the best route to trace this data. Signing the SHA1 makes > > the most sense, but need to be able to do that without polluting the tag > > namespace. > Have the PM push over SSH, and don't ever expire reflogs on the > central repository? The reflog will have the old and new commits > and the user name of the PM. All pushing to the central repo will be git+ssh:// anyway. I don't follow where the PM's identity is being stored, and how that's distributed back out with the later pulls. The other downside to relying on SSH presentation of identity directly, is the inability to use the SSH key to uniquely identify the user during the SSH auth (see designs like gitosis, where you always push to git+ssh://git@host/repo). -- Robin Hugh Johnson Gentoo Linux Developer & Infra Guy E-Mail : robbat2@xxxxxxxxxx GnuPG FP : 11AC BA4F 4778 E3F6 E4ED F38E B27B 944E 3488 4E85
Attachment:
pgpHkiNDGmsK3.pgp
Description: PGP signature