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

Re: Tracking branch history

From
Junio C Hamano <junkio@cox.net>
Date
May 13, 2006, 04:56 UTC
Message-ID
<7vody2v7yr.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20060513034051.GA21586@spearce.org>
Shawn Pearce <spearce@spearce.org> writes:
Show 16 quoted lines
> git-udpate-ref.  So just have it append the ref's history to a file:
>
> 	.git/log/refs/heads/$branch
>
> where the history records are stored as:
>
> 	40 byte commit-ish SHA1
> 	<SP>
> 	<committer>
> 	<LF>
>
> e.g.:
>
> 	cbb6d91d95e523c2b6a6b52577c4be28d18ace83 Shawn O. Pearce <spearce@spearce.org> 1137039378 -0500
> 	ae8c74e96a1e02bbfb7f1a9669b77d6f8ee6c3cf Shawn O. Pearce <spearce@spearce.org> 1136921470 -0500
>

Because the question we often would want to ask is "two days ago my tip worked but today it does not", recording the timestamp makes sense, but I do not know what the point is for the name and e-mail. If it is in your local repository (i.e. the program that updates the tip ref is not receive-pack which is invoked by your pushing into a remote repo), it will always be you. And in the receive-pack case, the information is not available to begin with (you may have a UNIX UID but that is about it).

Previous: Linus TorvaldsNext: Shawn Pearce
Message 7 of 21 in “Tracking branch history”
  1. Daniel BarkalowMay 12, 2006
  2. Linus TorvaldsMay 12, 2006
  3. Linus TorvaldsMay 13, 2006
  4. Daniel BarkalowMay 13, 2006
  5. Shawn PearceMay 13, 2006
  6. Linus TorvaldsMay 13, 2006
  7. Junio C HamanoMay 13, 2006
  8. Shawn PearceMay 13, 2006
  9. Shawn PearceMay 13, 2006
  10. Linus TorvaldsMay 13, 2006
  11. Junio C HamanoMay 13, 2006
  12. Shawn PearceMay 13, 2006
  13. Junio C HamanoMay 14, 2006
  14. Shawn PearceMay 15, 2006
  15. Shawn PearceMay 15, 2006
  16. Junio C HamanoMay 15, 2006
  17. Shawn PearceMay 15, 2006
  18. Shawn PearceMay 15, 2006
  19. Linus TorvaldsMay 13, 2006
  20. ElrondMay 13, 2006
  21. Junio C HamanoMay 14, 2006

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.