From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Andreas Ericsson <ae@op5.se>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git.org registered
Date: 12 Nov 2005 04:30:06 -0800 [thread overview]
Message-ID: <86wtjem4kx.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <4375DF45.3020301@op5.se>
>>>>> "Andreas" == Andreas Ericsson <ae@op5.se> writes:
Andreas> git.org has just been registered (well, "just" being what www.git.org says).
Andreas> Might be nothing and it might be someone hitching a free ride.
Andreas> I just thought you all ought to know.
Might be a good time to register gitsoftware.org for future use.
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
next prev parent reply other threads:[~2005-11-12 12:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-12 12:25 git.org registered Andreas Ericsson
2005-11-12 12:30 ` Randal L. Schwartz [this message]
2005-11-12 12:42 ` Petr Baudis
2005-11-12 12:50 ` Adrien Beau
2005-11-13 13:27 ` Edésio Costa e Silva
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=86wtjem4kx.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=ae@op5.se \
--cc=git@vger.kernel.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).