{"thread":{"id":"45259","subject":"[PATCH] README: create HTTP/HTTPS links from URLs in Markdown","startedAt":"2017-03-01T23:17:04Z","lastAt":"2017-03-02T14:26:17Z","messageCount":5,"participants":["Eric Wong","Jeff King"],"isPatch":true,"patchVersion":1,"patchTotal":null},"messages":[{"id":"313004","messageId":"20170301222204.GA5413@whir","threadId":"45259","inReplyTo":null,"subject":"[PATCH] README: create HTTP/HTTPS links from URLs in Markdown","fromName":"Eric Wong","fromEmail":"e@80x24.org","sentAt":"2017-03-01T22:22:04Z","receivedAt":"2017-03-01T23:17:04Z","isPatch":true,"sender":{"key":"e@80x24.org","avatar":null},"body":"Markdown supports automatic links by surrounding URLs with\nangle brackets, as documented in\n\n\nWhile we're at it, update URLs to avoid redirecting clients for\ngit-scm.com (by using HTTPS) and public-inbox.org (by adding a\ntrailing slash).\n\nSigned-off-by: Eric Wong \n---\n I was going to cite some style manuals (MLA, APA, etc),\n but it seems current versions do not favor angle brackets.\n However, this remains consistent with the recommendations in\n RFC 2369 for mail headers.\n\n README.md | 6 +++---\n 1 file changed, 3 insertions(+), 3 deletions(-)\n\ndiff --git a/README.md b/README.md\nindex c0cd5580e..f17af66a9 100644\n--- a/README.md\n+++ b/README.md\n@@ -12,7 +12,7 @@ Torvalds with help of a group of hackers around the net.\n \n Please read the file [INSTALL][] for installation instructions.\n \n-Many Git online resources are accessible from http://git-scm.com/\n+Many Git online resources are accessible from \n including full documentation and Git related tools.\n \n See [Documentation/gittutorial.txt][] to get started, then see\n@@ -33,8 +33,8 @@ requests, comments and patches to git@vger.kernel.org (read\n [Documentation/SubmittingPatches][] for instructions on patch submission).\n To subscribe to the list, send an email with just \"subscribe git\" in\n the body to majordomo@vger.kernel.org. The mailing list archives are\n-available at https://public-inbox.org/git,\n-http://marc.info/?l=git and other archival sites.\n+available at ,\n+ and other archival sites.\n \n The maintainer frequently sends the \"What's cooking\" reports that\n list the current status of various development topics to the mailing\n-- \nEW\n"},{"id":"313042","messageId":"20170302073708.dxm4p24pt6zlqjuz@sigill.intra.peff.net","threadId":"45259","inReplyTo":"20170302073421.GA2528@whir","subject":"Re: [PATCH] README: create HTTP/HTTPS links from URLs in Markdown","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2017-03-02T07:37:09Z","receivedAt":"2017-03-02T07:37:46Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Thu, Mar 02, 2017 at 07:34:21AM +0000, Eric Wong wrote:\n\n> Jeff King wrote:\n> > On Wed, Mar 01, 2017 at 10:22:04PM +0000, Eric Wong wrote:\n> > \n> > > Markdown supports automatic links by surrounding URLs with\n> > > angle brackets, as documented in\n> > > \n> > \n> > One of the joys of markdown is that there are so many variants. A lot of\n> > them (including GitHub-flavored markdown) will linkify URLs even when\n> > they're not inside angle brackets.\n> > \n> > So I don't mind this patch, but I'm curious what's rendering the\n> > markdown you're seeing. I'd think online that one would either come\n> > across the raw text, or the GFM from https://github.com/git/git.\n> \n> I was using Gruber's reference implementation from Debian stable\n> (1.0.1-7).\n\nOK. I guess my question more was \"why are you doing that?\". I'd expect\npeople to find the GFM rendering on GitHub, or just look at the text via\n\"less\".\n\nBut it's not really my business why you would want to do it. :) It's\nreasonable for us to cater to the common subset of renderers.\n\n-Peff\n"},{"id":"313043","messageId":"20170302073421.GA2528@whir","threadId":"45259","inReplyTo":"20170302071810.pbczh3p4w4bnyqzg@sigill.intra.peff.net","subject":"Re: [PATCH] README: create HTTP/HTTPS links from URLs in Markdown","fromName":"Eric Wong","fromEmail":"e@80x24.org","sentAt":"2017-03-02T07:34:21Z","receivedAt":"2017-03-02T08:11:34Z","isPatch":true,"sender":{"key":"e@80x24.org","avatar":null},"body":"Jeff King wrote:\n> On Wed, Mar 01, 2017 at 10:22:04PM +0000, Eric Wong wrote:\n> \n> > Markdown supports automatic links by surrounding URLs with\n> > angle brackets, as documented in\n> > \n> \n> One of the joys of markdown is that there are so many variants. A lot of\n> them (including GitHub-flavored markdown) will linkify URLs even when\n> they're not inside angle brackets.\n> \n> So I don't mind this patch, but I'm curious what's rendering the\n> markdown you're seeing. I'd think online that one would either come\n> across the raw text, or the GFM from https://github.com/git/git.\n\nI was using Gruber's reference implementation from Debian stable\n(1.0.1-7).\n\nAlso, pandoc (also Debian stable 1.12.4.2~dfsg-1+b14) seems to\nrequire angle brackets by default. pandoc also supports the\n\"-f markdown_github\" option where it seems to behave like GFM.\n\nBut yeah, I much prefer the unambiguity of angle brackets,\nespecially when URLs are followed immediately but punctuation\nsuch as ',' or '.'.\n"},{"id":"313053","messageId":"20170302075709.GA6295@starla","threadId":"45259","inReplyTo":"20170302073708.dxm4p24pt6zlqjuz@sigill.intra.peff.net","subject":"Re: [PATCH] README: create HTTP/HTTPS links from URLs in Markdown","fromName":"Eric Wong","fromEmail":"e@80x24.org","sentAt":"2017-03-02T07:57:09Z","receivedAt":"2017-03-02T08:52:12Z","isPatch":true,"sender":{"key":"e@80x24.org","avatar":null},"body":"Jeff King wrote:\n> On Thu, Mar 02, 2017 at 07:34:21AM +0000, Eric Wong wrote:\n> > Jeff King wrote:\n> > > On Wed, Mar 01, 2017 at 10:22:04PM +0000, Eric Wong wrote:\n> > > \n> > > > Markdown supports automatic links by surrounding URLs with\n> > > > angle brackets, as documented in\n> > > > \n> > > \n> > > One of the joys of markdown is that there are so many variants. A lot of\n> > > them (including GitHub-flavored markdown) will linkify URLs even when\n> > > they're not inside angle brackets.\n> > > \n> > > So I don't mind this patch, but I'm curious what's rendering the\n> > > markdown you're seeing. I'd think online that one would either come\n> > > across the raw text, or the GFM from https://github.com/git/git.\n> > \n> > I was using Gruber's reference implementation from Debian stable\n> > (1.0.1-7).\n> \n> OK. I guess my question more was \"why are you doing that?\". I'd expect\n> people to find the GFM rendering on GitHub, or just look at the text via\n> \"less\".\n\nActually, I was initially seeing the lack of trailing slash\ncausing unnecessary 301 redirects on public-inbox.org.\n\nSo, I added the trailing slash and ran \"markdown But it's not really my business why you would want to do it. :) It's\n> reasonable for us to cater to the common subset of renderers.\n\n:)\n\nI figure somebody unfamiliar with Markdown editing README.md is\nlikely to run the original implementation locally to check their\nwork, as I did.\n\n\n(hmm... and vger is unusually slow this week)\n"},{"id":"313067","messageId":"20170302071810.pbczh3p4w4bnyqzg@sigill.intra.peff.net","threadId":"45259","inReplyTo":"20170301222204.GA5413@whir","subject":"Re: [PATCH] README: create HTTP/HTTPS links from URLs in Markdown","fromName":"Jeff King","fromEmail":"peff@peff.net","sentAt":"2017-03-02T07:18:10Z","receivedAt":"2017-03-02T14:26:17Z","isPatch":true,"sender":{"key":"peff@peff.net","avatar":"https://avatars.githubusercontent.com/u/45925?v=4"},"body":"On Wed, Mar 01, 2017 at 10:22:04PM +0000, Eric Wong wrote:\n\n> Markdown supports automatic links by surrounding URLs with\n> angle brackets, as documented in\n> \n\nOne of the joys of markdown is that there are so many variants. A lot of\nthem (including GitHub-flavored markdown) will linkify URLs even when\nthey're not inside angle brackets.\n\nSo I don't mind this patch, but I'm curious what's rendering the\nmarkdown you're seeing. I'd think online that one would either come\nacross the raw text, or the GFM from https://github.com/git/git.\n\n-Peff\n"}]}