From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: main url for linking to git source?
Date: Mon, 7 May 2018 07:38:06 -0400 (DST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1805070731580.77@tvgsbejvaqbjf.bet> (raw)
In-Reply-To: <20180507063713.GA28961@sigill.intra.peff.net>
Hi Peff,
On Mon, 7 May 2018, Jeff King wrote:
> The git-scm.com site currently links to https://github.com/git/git for
> the (non-tarball) source code. Somebody raised the question[1] of
> whether it should point to kernel.org instead.
>
> Do people find one interface more or less pleasing than the other? Do we
> want to prefer kernel.org as more "official" or less commercial?
I don't really care about "official" vs "commercial", as kernel.org is
also run by a business, so it is all "commercial" to me.
Personally, I prefer the GitHub interface. A *lot*. Why?
- it is faster
- it is prettier
- you can fork easily
- it also has the Continuous Integration, well, integrated
- it is a lot easier to link to individual commits/files/lines
- the links are *a lot* nicer
- you can provide a <repo>/compare/A...B link to a specific, possibly
dynamic commit range
I do not have anything against listing kernel.org, *in addition*. But
kernel.org is just simply so much more limited, and less pretty, so I
really think that the PR is misguided and would do more harm than good.
Ciao,
Dscho
next prev parent reply other threads:[~2018-05-07 11:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 6:37 main url for linking to git source? Jeff King
2018-05-07 11:38 ` Johannes Schindelin [this message]
2018-05-07 14:20 ` Konstantin Ryabitsev
2018-05-07 12:18 ` Junio C Hamano
2018-05-07 18:15 ` Stefan Beller
2018-05-08 1:51 ` brian m. carlson
2018-05-08 2:46 ` Konstantin Ryabitsev
2018-05-08 3:26 ` Junio C Hamano
2018-05-08 12:55 ` brian m. carlson
2018-05-08 6:43 ` Kaartic Sivaraam
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.1805070731580.77@tvgsbejvaqbjf.bet \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).