Shawn Pearce <spearce@xxxxxxxxxxx> writes: > git-udpate-ref. So just have it append the ref's history to a file: > > .git/log/refs/heads/$branch > > where the history records are stored as: > > 40 byte commit-ish SHA1 > <SP> > <committer> > <LF> > > e.g.: > > cbb6d91d95e523c2b6a6b52577c4be28d18ace83 Shawn O. Pearce <spearce@xxxxxxxxxxx> 1137039378 -0500 > ae8c74e96a1e02bbfb7f1a9669b77d6f8ee6c3cf Shawn O. Pearce <spearce@xxxxxxxxxxx> 1136921470 -0500 > Because the question we often would want to ask is "two days ago my tip worked but today it does not", recording the timestamp makes sense, but I do not know what the point is for the name and e-mail. If it is in your local repository (i.e. the program that updates the tip ref is not receive-pack which is invoked by your pushing into a remote repo), it will always be you. And in the receive-pack case, the information is not available to begin with (you may have a UNIX UID but that is about it). - : 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