From: Junio C Hamano <junkio@cox.net>
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: [REQ] git-announce mailing list
Date: Wed, 21 Sep 2005 13:14:04 -0700 [thread overview]
Message-ID: <7vr7bitbzn.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20050921143231.GA21971@pasky.or.cz> (Petr Baudis's message of "Wed, 21 Sep 2005 16:32:31 +0200")
Petr Baudis <pasky@suse.cz> writes:
> 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?
I did not because I felt anything other than the following three
would be just adding noise to already high traffic:
(1) "I am the vger.kernel.org list maintainer and I will create
one".
(2) "I do not have enough time to keep up with git list but I
want to get only announce -- count me in please".
(3) "It is not a good idea because...".
and whatever I would have said would not have been any of the
above.
next prev parent reply other threads:[~2005-09-21 20:14 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
2005-09-21 20:14 ` Junio C Hamano [this message]
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=7vr7bitbzn.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
/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.