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

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

From
Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Date
Aug 5, 2006, 23:55 UTC
Message-ID
<200608060155.06723.robin.rosenberg.lists@dewire.com>
In-Reply-To
<001a01c6b8cd$0a7b5860$c47eedc1@ramsay1.demon.co.uk>
> 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.

Couldn't you track git with another machine? Then copy that clone to your linux box and then do a local pull from the copied clone. 

There's also the http_proxy, but I guess you know that already.
-- robin
Previous: Shawn Pearce
Message 5 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.