From: Jonathan Nieder <jrnieder@gmail.com>
To: David Kastrup <dak@gnu.org>
Cc: Jeff King <peff@peff.net>, Scott Chacon <schacon@gmail.com>,
Christian Couder <christian.couder@gmail.com>,
Shawn Pearce <spearce@spearce.org>,
Michael J Gruber <git@drmicha.warpmail.net>,
Junio C Hamano <gitster@pobox.com>, git <git@vger.kernel.org>
Subject: Re: git-scm.com website
Date: Mon, 9 Mar 2015 14:07:07 -0700 [thread overview]
Message-ID: <20150309210707.GC5535@google.com> (raw)
In-Reply-To: <878uf5lyad.fsf@fencepost.gnu.org>
Hi,
David Kastrup wrote:
> Jeff King <peff@peff.net> writes:
>> If people don't like git-scm.com and want to have an alternate site,
>
> I think that's the basic problem here.
With all due respect:
I don't actually see a major problem here. Any serious problems with
the site can be fixed by people submitting patches, either using
Github's UI or to the mailing list if Github's UI doesn't work for
them. People can also try mocking up an alternative site if they have
a radical change they'd like to try, and the centrally managed DNS
entry points to whichever site is appropriate.
The old git website was git.or.cz. That redirects to git-scm.com now.
You can see the old front page at git.or.cz/index.html (and there is a
link to the corresponding git repository near the bottom). People
with spare time who find content on that site to migrate over are
welcome to try doing so (hint, hint).
Thanks,
Jonathan
next prev parent reply other threads:[~2015-03-09 21:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-09 15:51 git-scm.com website (was: Promoting Git developers) Shawn Pearce
2015-03-09 16:06 ` git-scm.com website David Kastrup
2015-03-09 16:19 ` Shawn Pearce
2015-03-09 16:37 ` David Kastrup
2015-03-09 17:12 ` Christian Couder
2015-03-09 17:52 ` Scott Chacon
2015-03-09 19:24 ` Jeff King
2015-03-09 20:18 ` David Kastrup
2015-03-09 21:07 ` Jonathan Nieder [this message]
2015-03-09 17:14 ` Scott Chacon
2015-03-09 17:30 ` Stefan Beller
2015-03-09 17:49 ` David Kastrup
2015-03-09 17:54 ` Stefan Beller
2015-03-09 18:02 ` David Kastrup
2015-03-10 9:07 ` Michael J Gruber
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=20150309210707.GC5535@google.com \
--to=jrnieder@gmail.com \
--cc=christian.couder@gmail.com \
--cc=dak@gnu.org \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=schacon@gmail.com \
--cc=spearce@spearce.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).