From: Shawn Pearce <spearce@spearce.org>
To: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
Cc: git@vger.kernel.org
Subject: Re: update-ref logs: problem with committer info?
Date: Sat, 5 Aug 2006 16:33:04 -0400 [thread overview]
Message-ID: <20060805203304.GB20565@spearce.org> (raw)
In-Reply-To: <001a01c6b8cd$0a7b5860$c47eedc1@ramsay1.demon.co.uk>
Ramsay Jones <ramsay@ramsay1.demon.co.uk> wrote:
>
> 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.
next prev parent reply other threads:[~2006-08-05 20:33 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 [this message]
2006-08-05 23:55 ` Robin Rosenberg
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=20060805203304.GB20565@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=ramsay@ramsay1.demon.co.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.