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, 16:43 UTC
Message-ID
<7vbqu1vps3.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.64.0605130815550.3866@g5.osdl.org>
Linus Torvalds <torvalds@osdl.org> writes:
> I actually disagree with Junio - I think the logging the name made sense. 
> If you have a shared repo with multiple people pushing to the same branch, 
> it's interesting to see who does the pushing.
Yes, I agree recording that information is interesting.

My comment was about how it is recorded. In the local case GIT_COMMITTER_IDENT is what you want as Shawn did in his original proposal, but remote "pushing into shared repository" case I do not think it is available in general.

Well, at least that was what I was thinking when I made that comment. However,

If the pushers arrange to have appropriate environment variables while receive-pack does its work (.git/config in the target repository is not an appropriate place to get user.* settings from in a shared setting), what you say makes perfect sense.

Having the usual enviornment available would be handy to make the hooks on the receiving end to do useful things anyway, so I retract that suggestion.

Show 6 quoted lines
> I also think it might be good to save the oldsha1 value. Yes, it _should_ 
> always be the previous sha1 logged, but it's interesting to see in case it 
> isn't (ie the ref was updated some other way), and it's also interesting 
> for the first entry after logging has been enabled.
>
> 		Linue

Yes, and also what user-level command was used to cause update the ref; was it a merge from remote, own commit, rewind/rebase?

	Junia
;-)
Previous: Linus TorvaldsNext: Shawn Pearce
Message 11 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.