git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Tracability in git commits

From
Ping Yin <pkufranky@gmail.com>
Date
May 1, 2008, 05:09 UTC
Message-ID
<46dff0320804302209o2af9d630s48564a9b68c24ec1@mail.gmail.com>
In-Reply-To
<20080501002827.GX29771@spearce.org>
On Thu, May 1, 2008 at 8:28 AM, Shawn O. Pearce <spearce@spearce.org> wrote:
Show 8 quoted lines
>  `git config core.logAllRefUpdates true` right after you make the
>  repository solves that nicely.  I actually have a script that I use
>  to make a new bare central repo:
>
>         #!/bin/sh
>         git --git-dir="$1" init &&
>         git --git-dir="$1" config core.logAllRefUpdates true ||
>         exit

I wonder why not make it the default behaviour. If someone push the wrong commit to the bare repository (for example, with 'git push -f'), there is no easy way to recover without reflog.

So as a solution, i would rather put this config to ~/.gitconfig
-- 
Ping Yin
Previous: Shawn O. PearceNext: Jakub Narebski
Message 9 of 15 in “Tracability in git commits”
  1. Richard PurdieApr 29, 2008
  2. Johannes SchindelinApr 29, 2008
  3. Junio C HamanoApr 29, 2008
  4. Richard PurdieApr 29, 2008
  5. Shawn O. PearceApr 30, 2008
  6. Ping YinApr 30, 2008
  7. Miklos VajnaApr 30, 2008
  8. Shawn O. PearceMay 1, 2008
  9. Ping YinMay 1, 2008
  10. Jakub NarebskiApr 30, 2008
  11. Richard PurdieApr 30, 2008
  12. Martin LanghoffMay 1, 2008
  13. Martin LanghoffMay 1, 2008
  14. Junio C HamanoMay 1, 2008
  15. Martin LanghoffMay 1, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.