git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Stefan Beller <sbeller@google.com>
To: Jeff King <peff@peff.net>
Cc: git <git@vger.kernel.org>
Subject: Re: main url for linking to git source?
Date: Mon, 7 May 2018 11:15:46 -0700	[thread overview]
Message-ID: <CAGZ79kZVdiEOO+b_Ygrfw1D9uV1T5TYBS580zPaZeYoMRfNuUQ@mail.gmail.com> (raw)
In-Reply-To: <20180507063713.GA28961@sigill.intra.peff.net>

Hi Jeff,

On Sun, May 6, 2018 at 11:37 PM, Jeff King <peff@peff.net> 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 could see arguments both ways, so I thought I'd take a straw poll of
> what people on the list think.

That PR is changing quite a few places, so in classic Git community
fashion, I advise to break it up into more patches. ;)

Junios reply below focuses on the URL passed to git-clone, which
is only found at https://git-scm.com/downloads (?)

There I would try to mirror Junios list of "public repositories"
https://git-blame.blogspot.com/p/git-public-repositories.html
without officially endorsing one over another.

For those links that link to web pages, I am ok with any of the
hosting providers, maybe even taking the one with the prettiest
web page. Maybe we want to reword those sections to rely
more on indirection, e.g. "get the source[link to the source page],
checkout the next branch", without the quick web link to a web page
showing the 'next' tree. Any of the pages with the 'next' tree
do not really help for the purpose of spotting which development
is currently happening. Maybe a "log --merges" would be better.
Something like https://kernel.googlesource.com/pub/scm/git/git/+log/next
(Not that I am endorsing this link over others. I just happen to know
that this comes close to what I propose having there)

Kernel.org might feel a bit more official than the others because
Linus started it there? And given that it is a non profit, I feel
better to link to them over any other commercial entity.

Hope that helps,
Stefan

  parent reply	other threads:[~2018-05-07 18:15 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
2018-05-07 14:20   ` Konstantin Ryabitsev
2018-05-07 12:18 ` Junio C Hamano
2018-05-07 18:15 ` Stefan Beller [this message]
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=CAGZ79kZVdiEOO+b_Ygrfw1D9uV1T5TYBS580zPaZeYoMRfNuUQ@mail.gmail.com \
    --to=sbeller@google.com \
    --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).