From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS31976 209.132.180.0/23 X-Spam-Status: No, score=-3.3 required=3.0 tests=AWL,BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_HI,RP_MATCHES_RCVD shortcircuit=no autolearn=ham autolearn_force=no version=3.4.0 Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by dcvr.yhbt.net (Postfix) with ESMTP id C33F420133 for ; Thu, 2 Mar 2017 08:52:09 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754237AbdCBIvm (ORCPT ); Thu, 2 Mar 2017 03:51:42 -0500 Received: from dcvr.yhbt.net ([64.71.152.64]:58426 "EHLO dcvr.yhbt.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754082AbdCBIvk (ORCPT ); Thu, 2 Mar 2017 03:51:40 -0500 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 6D12A2027B; Thu, 2 Mar 2017 07:57:09 +0000 (UTC) Date: Thu, 2 Mar 2017 07:57:09 +0000 From: Eric Wong To: Jeff King Cc: Junio C Hamano , git@vger.kernel.org Subject: Re: [PATCH] README: create HTTP/HTTPS links from URLs in Markdown Message-ID: <20170302075709.GA6295@starla> References: <20170301222204.GA5413@whir> <20170302071810.pbczh3p4w4bnyqzg@sigill.intra.peff.net> <20170302073421.GA2528@whir> <20170302073708.dxm4p24pt6zlqjuz@sigill.intra.peff.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20170302073708.dxm4p24pt6zlqjuz@sigill.intra.peff.net> Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Jeff King wrote: > On Thu, Mar 02, 2017 at 07:34:21AM +0000, Eric Wong wrote: > > Jeff King wrote: > > > On Wed, Mar 01, 2017 at 10:22:04PM +0000, Eric Wong wrote: > > > > > > > Markdown supports automatic links by surrounding URLs with > > > > angle brackets, as documented in > > > > > > > > > > One of the joys of markdown is that there are so many variants. A lot of > > > them (including GitHub-flavored markdown) will linkify URLs even when > > > they're not inside angle brackets. > > > > > > So I don't mind this patch, but I'm curious what's rendering the > > > markdown you're seeing. I'd think online that one would either come > > > across the raw text, or the GFM from https://github.com/git/git. > > > > I was using Gruber's reference implementation from Debian stable > > (1.0.1-7). > > OK. I guess my question more was "why are you doing that?". I'd expect > people to find the GFM rendering on GitHub, or just look at the text via > "less". Actually, I was initially seeing the lack of trailing slash causing unnecessary 301 redirects on public-inbox.org. So, I added the trailing slash and ran "markdown But it's not really my business why you would want to do it. :) It's > reasonable for us to cater to the common subset of renderers. :) I figure somebody unfamiliar with Markdown editing README.md is likely to run the original implementation locally to check their work, as I did. (hmm... and vger is unusually slow this week)