From: Matthieu Moy <Matthieu.Moy@imag.fr>
To: Stephen Haberman <stephen@exigencecorp.com>
Cc: git@vger.kernel.org
Subject: Re: [announce] gc
Date: Tue, 23 Dec 2008 14:13:49 +0100 [thread overview]
Message-ID: <vpqabanc9v6.fsf@bauges.imag.fr> (raw)
In-Reply-To: <20081222212407.47c9ab1e.stephen@exigencecorp.com> (Stephen Haberman's message of "Mon\, 22 Dec 2008 21\:24\:07 -0600")
Stephen Haberman <stephen@exigencecorp.com> writes:
> Hi,
>
> This is just a small collections of hooks, scripts, and practices I
> developed while working on a not-distributed/corporate project.
You should find a better name. I mean, one for which
http://www.google.com/search?q=git+YOUR-NAME-HERE
has a chance to find you ...
My 2 cents,
--
Matthieu
next prev parent reply other threads:[~2008-12-23 13:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-23 3:24 [announce] gc Stephen Haberman
2008-12-23 13:13 ` Matthieu Moy [this message]
2008-12-23 14:22 ` Stephen Haberman
2008-12-23 15:06 ` Mike Ralphson
2008-12-25 15:23 ` Stephen Haberman
2009-01-14 1:31 ` Jakub Narebski
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=vpqabanc9v6.fsf@bauges.imag.fr \
--to=matthieu.moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=stephen@exigencecorp.com \
/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).