git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: Pat Notz <patnotz@gmail.com>,
	"Shawn O. Pearce" <spearce@spearce.org>,
	Git <git@vger.kernel.org>
Subject: Re: Gnome chose Git
Date: Fri, 20 Mar 2009 16:03:46 -0400	[thread overview]
Message-ID: <20090320200346.GD26934@coredump.intra.peff.net> (raw)
In-Reply-To: <49C354CC.2020108@drmicha.warpmail.net>

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

      reply	other threads:[~2009-03-20 20:05 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-19 11:23 Gnome chose Git Teemu Likonen
2009-03-19 11:29 ` Sverre Rabbelier
2009-03-19 11:33 ` Mike Ralphson
2009-03-19 16:29   ` Andreas Ericsson
2009-03-19 13:33 ` Michael J Gruber
     [not found]   ` <1cd1989b0903190643p19a40718yc4fd2730aab0a9a0@mail.gmail.com>
     [not found]     ` <49C24D9B.1060301@drmicha.warpmail.net>
2009-03-19 14:01       ` Pat Notz
2009-03-19 15:16         ` Shawn O. Pearce
2009-03-19 15:50           ` Pat Notz
2009-03-19 20:14             ` Jeff King
2009-03-19 21:40               ` demerphq
2009-03-19 21:43                 ` Shawn O. Pearce
2009-03-19 21:44                   ` Shawn O. Pearce
2009-03-19 21:51                     ` demerphq
2009-03-19 21:53                       ` Shawn O. Pearce
2009-03-19 21:59                         ` demerphq
2009-03-19 23:17                       ` Johannes Schindelin
2009-03-19 21:48                   ` demerphq
2009-03-20  5:28                   ` Jeff King
2009-03-20  6:00                     ` [PATCH] make oneline reflog dates more consistent with multiline format Jeff King
2009-03-20  8:33               ` Gnome chose Git Michael J Gruber
2009-03-20 20:03                 ` Jeff King [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090320200346.GD26934@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=patnotz@gmail.com \
    --cc=spearce@spearce.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).