On Fri, Mar 20, 2009 at 09:33:16AM +0100, Michael J Gruber wrote: > > But do note that reflogs expire eventually, so you will want to also > > look at gc.reflogexpire and gc.reflogexpireunreachable if you want to > > keep this as an activity log forever. > > In any case, reflogs are local. I would assume that accountability > tracking should be public and transparent. Depends on the use case, of > course. I think the use case was auditing "when did this code get into the repo, and by whom". Which is inherently a local thing, since you are talking about when it got into a central repo. As for public and transparent, reflogs are only the database mechanism; git already has the hooks in place for writing every ref change to this mechanism, and it stores everything you need. They would just need some way of publishing the information. I think it was you who suggested notes, which would be one way of doing so; you could also publish tags indexed by pusher (since we may or may not actually care about fast lookup from commit to pusher here), or even just a web page. -Peff -- 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
