> -----Original Message-----
> From:
repo-d...@googlegroups.com [mailto:
repo-
>
dis...@googlegroups.com] On Behalf Of Magnus Bäck
>
> On Wednesday, May 23, 2012 at 10:13 EDT,
> Martin Fick <
mf...@codeaurora.org> wrote:
>
> > "Magnus Bäck" <
ba...@google.com> wrote:
> >
> > > Only if you can dig up the offending receive-pack command from
> > > sshd_log. There is no explicit logging of ref delete operations,
> > > and if the deletion is made from the UI there's AFAICT no success
> > > logging at all. There probably should be.
> >
> > You are not the first to ask this, and I think this is a very
> > legitimate request. I suggest that you post a request to log
> > deletes to the GIT mailing list since it would be good to get
> > this defined at the GIT level.
>
> How would this be defined at the Git level, given that Git doesn't
> perform any logging besides stdout/stderr messages? Are you saying Git
It could, if you ask it.
core.logAllRefUpdates = true
Putting option behind a 'git config' command will make git log ref updates in logs/refs/$REFNAME if I understood things correctly.
Not sure which git version it was introduced in.
> should say something about performed deletions in the receive-pack
> output that's (I guess) fed back to clients?
Undoubtedly it could use some better presentation than in a file on the server side git, granted.
> I think Gerrit's logging can be improved in general, but that's a
> topic for another thread.
I agree on this too, it was not easy as an administrator to get in to gerrit logs. It's still too programmatic in many senses.
--
Best regards,
Fredrik Luthander
Sony Mobile Communications AB