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

Re: update-ref logs: problem with committer info?

From
Shawn Pearce <spearce@spearce.org>
Date
Aug 5, 2006, 20:33 UTC
Message-ID
<20060805203304.GB20565@spearce.org>
In-Reply-To
<001a01c6b8cd$0a7b5860$c47eedc1@ramsay1.demon.co.uk>
Ramsay Jones <ramsay@ramsay1.demon.co.uk> wrote:
Show 5 quoted lines
> 
> Yes, I am quite a long way behind, at version 1.4.1, which is light-years
> in git-time!  Unfortunately, since I can't pull from the git repo (I don't
> have internet access from Linux), I won't be able to update until the v1.4.2
> tar-ball is posted. Yep, not exactly ideal.
Yea, that's not much fun.  I found that tracking GIT with GIT is
really the easiest way to stay current.  Not having direct net
access makes that nearly impossible.
 
> OK, for now I will refrain from contributing, at least until v1.4.2 is out.
> 
> Sorry for the noise.

Its not noise, three of your five changes were current bugs that needed fixing. :-)

-- 
Shawn.
Previous: Ramsay JonesNext: Robin Rosenberg
Message 4 of 5 in “update-ref logs: problem with committer info?”
  1. Ramsay JonesAug 4, 2006
  2. Shawn PearceAug 5, 2006
  3. Ramsay JonesAug 5, 2006
  4. Shawn PearceAug 5, 2006
  5. Robin RosenbergAug 5, 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.