From: webmaster at eclipse.org (Eclipse Webmaster (Denis Roy))
Subject: git.zx2c4.com down ?
Date: Tue, 15 Jan 2013 16:19:45 -0500 [thread overview]
Message-ID: <50F5C7F1.2070207@eclipse.org> (raw)
In-Reply-To: <CAHmME9o_KKNkDGtP8QGvOhp4SEXKXnLzA7LX3ZyHsH2V5ZkOuQ@mail.gmail.com>
Jason,
Many thanks for assuming leadership of the project. cGit is great and
it's the Git front-end of choice here at Eclipse.
Healthy discussion is a sign of a healthy community. Folks asked
questions and they were shot down really quick. Had the email below
been presented several hours earlier, there would have been no need for
follow-up questions since your position is quite clear.
Again, many thanks to you personally for your hard work on cGit, and to
everyone who contributes. I hope the project continues to prosper as an
active community of involved users and developers who are all open to
discussion and to new ideas.
Denis
On 01/15/2013 04:03 PM, Jason A. Donenfeld wrote:
> Hi all,
>
> Let's end this discussion before it turns into cgit mailinglist's
> first ever flamewar. That would be a good thing to do.
>
> Stefan, thanks for your input. Jamie and Dzen, thanks too for yours --
> I think you guys are right. The mailing list patch model of cgit works
> well, most of us all seem to like it, and I have no intentions on
> changing how we operate.
>
> Further, dog-fooding is a good thing: if there's a shortcoming in cgit
> that makes it inadequate for development of cgit, well, then we've got
> our work cut out for us. But things have been working very well (I
> think), and I like the community and processes Lars began. I do not
> plan to change these in the immediate future.
>
> Finally, thanks for the email about the downtime. There were indeed a
> few moments of downtime as hosting records were updated to juice up my
> server, and I don't anticipate there'll be significant downtime in the
> future.
>
> Ending this discussion before the flames begin would be a Good Thing
> To Do (tm). I sincerely hope this message is the last of the thread,
> and I'd encourage others not to really entertain it any further.
>
> Jason
>
next prev parent reply other threads:[~2013-01-15 21:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 14:21 stefan.naewe
2013-01-15 15:36 ` Jason
2013-01-15 15:40 ` stefan.naewe
2013-01-15 15:48 ` mailings
2013-01-15 15:57 ` Jason
2013-01-15 16:02 ` stefan.naewe
2013-01-15 16:15 ` Jason
2013-01-15 19:15 ` stefan.naewe
2013-01-15 20:14 ` jamie.couture
2013-01-15 20:22 `
2013-01-15 20:35 ` stefan.naewe
2013-01-15 21:03 ` Jason
2013-01-15 21:19 ` webmaster [this message]
2013-01-15 21:26 ` mailings
2013-01-15 21:55 `
2013-01-15 22:02 ` mailings
2013-01-15 15:58 ` Jason
2013-01-15 23:55 ` normalperson
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=50F5C7F1.2070207@eclipse.org \
--to=cgit@lists.zx2c4.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).