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
Apr 30, 2008, 17:33 UTC
Message-ID
<46dff0320804301033k1dea34ecx863ecfa8e386e0af@mail.gmail.com>
In-Reply-To
<7vd4o873cm.fsf@gitster.siamese.dyndns.org>
On Wed, Apr 30, 2008 at 5:34 AM, Junio C Hamano <gitster@pobox.com> wrote:
>  is updated, using that added part of the history.  The updates to the tip
>  will be recorded in reflog to record who updated the tip and when, which
>  would allow you to go back and point your finger at the person who
>  introduced problematic new history
I don't find reflog for bare repository, or must i enable it manually?
-- 
Ping Yin
Previous: Shawn O. PearceNext: Miklos Vajna
Message 6 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.