From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: "Ramsay Jones" <ramsay@ramsay1.demon.co.uk>
Cc: spearce@spearce.org, git@vger.kernel.org
Subject: RE: update-ref logs: problem with committer info?
Date: Sun, 6 Aug 2006 01:55:05 +0200 [thread overview]
Message-ID: <200608060155.06723.robin.rosenberg.lists@dewire.com> (raw)
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
prev parent reply other threads:[~2006-08-05 23:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-04 21:01 update-ref logs: problem with committer info? Ramsay Jones
2006-08-05 2:56 ` Shawn Pearce
2006-08-05 20:23 ` Ramsay Jones
2006-08-05 20:33 ` Shawn Pearce
2006-08-05 23:55 ` Robin Rosenberg [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200608060155.06723.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=git@vger.kernel.org \
--cc=ramsay@ramsay1.demon.co.uk \
--cc=spearce@spearce.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).