From: Petr Baudis <pasky@suse.cz>
To: Cal Peake <cp@absolutedigital.net>
Cc: Git Mailing List <git@vger.kernel.org>, postmaster@vger.kernel.org
Subject: Re: [REQ] git-announce mailing list
Date: Wed, 21 Sep 2005 16:32:31 +0200 [thread overview]
Message-ID: <20050921143231.GA21971@pasky.or.cz> (raw)
In-Reply-To: <Pine.LNX.4.61.0509060457130.29285@lancer.cnet.absolutedigital.net>
Dear diary, on Wed, Sep 14, 2005 at 10:42:50AM CEST, I got a letter
where Cal Peake <cp@absolutedigital.net> told me that...
> Any chance for a git-announce list on vger?
Did my fellow git-related maintainers not reply because they were
waiting to hpa to reply, and hpa not reply since he didn't see any
interest by the maintainers? Or something else happenned to this idea?
Would any other people find this useful?
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.
next prev parent reply other threads:[~2005-09-21 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-14 8:42 [REQ] git-announce mailing list Cal Peake
2005-09-21 14:32 ` Petr Baudis [this message]
2005-09-21 20:14 ` Junio C Hamano
2005-09-21 21:40 ` Johannes Schindelin
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=20050921143231.GA21971@pasky.or.cz \
--to=pasky@suse.cz \
--cc=cp@absolutedigital.net \
--cc=git@vger.kernel.org \
--cc=postmaster@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).