From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Subject: [RFC] what content should go in https://git-scm.com/doc/ext
Date: Sat, 21 Jan 2017 08:55:45 -0500 [thread overview]
Message-ID: <20170121135545.gi6crct66msylhpr@sigill.intra.peff.net> (raw)
I'm wondering if anybody has opinions on:
https://github.com/git/git-scm.com/pull/924
(and I suspect most people in this community do not read pull requests
there, hence this post).
Basically, we maintain a list of links to outside documentation, as well
as to books. Somebody has requested a link to their paid tutorial
course. How should we handle it?
If the resource is valuable, then it may make sense to link to it, even
if it costs money. We already do this with book links, and my policy has
been to link any relevant book that is requested (I don't read them for
quality, so I have no opinions).
Should we do the same for tutorial content like this?
-Peff
next reply other threads:[~2017-01-21 13:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-21 13:55 Jeff King [this message]
2017-01-22 19:13 ` [RFC] what content should go in https://git-scm.com/doc/ext Christian Couder
2017-01-25 18:42 ` Jeff King
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=20170121135545.gi6crct66msylhpr@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.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).