threads / discuss / 1795

[REQ] git-announce mailing list

Subject: [REQ] git-announce mailing list

## tl;dr

4 messages between Sep 14, 2005 and Sep 21, 2005.

replies: 3people: 4as markdown or json

Petr Baudis· Sep 21, 2005, 14:32 UTC · re: Cal Peake · lore

Re: [REQ] git-announce mailing list

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.
Junio C Hamano· Sep 21, 2005, 20:14 UTC · re: Petr Baudis · lore

Re: [REQ] git-announce mailing list

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.

Johannes Schindelin· Sep 21, 2005, 21:40 UTC · re: Junio C Hamano · lore

Re: [REQ] git-announce mailing list

Hi,
On Wed, 21 Sep 2005, Junio C Hamano wrote:
>  (3) "It is not a good idea because...".

... because at the current stage, changes happen very quickly, and very often. Most of the times, you really can only understand what the change is about if you

	1) happen to know how git was supposed to work before the change,
and
	2) happen to understand what is being discussed anyway.

I'll feel differently after 1.0 is released, mostly since I know that Junio will release it only after git grew up to be stable enough to evolve at a much slower pace. I expect mostly merge enhancements and porcelain improvements after that.

Ciao, Dscho

← back to recent threads