git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: git@vger.kernel.org, emma.westby@gmail.com
Subject: Re: [PATCH 1/5] README: use markdown syntax
Date: Tue, 23 Feb 2016 11:07:34 -0800	[thread overview]
Message-ID: <xmqqoab71c09.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <1456249229-30454-2-git-send-email-Matthieu.Moy@imag.fr> (Matthieu Moy's message of "Tue, 23 Feb 2016 18:40:25 +0100")

Matthieu Moy <Matthieu.Moy@imag.fr> writes:

> This allows repository browsers like GitHub to display the content of
> the file nicely formatted.
>
> Signed-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>
> ---

To be honest, I have the most problem with this step in the whole
series.

Markdown when rendered may be easier to read, but plain text is even
easier, and it somehow feels backward to cater to those who browse
at GitHub sacrificing those who use "less" in the source tree.

>  README => README.md | 6 +-----
>  t/t7001-mv.sh       | 2 +-
>  2 files changed, 2 insertions(+), 6 deletions(-)
>  rename README => README.md (93%)
>
> diff --git a/README b/README.md
> similarity index 93%
> rename from README
> rename to README.md
> index 1083735..907eb3b 100644
> --- a/README
> +++ b/README.md
> @@ -1,8 +1,4 @@
> -////////////////////////////////////////////////////////////////
> -
> -	Git - the stupid content tracker
> -
> -////////////////////////////////////////////////////////////////
> +# Git - the stupid content tracker
>  
>  "git" can mean anything, depending on your mood.
>  
> diff --git a/t/t7001-mv.sh b/t/t7001-mv.sh
> index 51dd2b4..4008fae 100755
> --- a/t/t7001-mv.sh
> +++ b/t/t7001-mv.sh
> @@ -102,7 +102,7 @@ test_expect_success \
>  
>  test_expect_success \
>      'adding another file' \
> -    'cp "$TEST_DIRECTORY"/../README path0/README &&
> +    'cp "$TEST_DIRECTORY"/../README.md path0/README &&
>       git add path0/README &&
>       git commit -m add2 -a'

  reply	other threads:[~2016-02-23 19:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-23 17:40 [RFC/PATCH 0/5] Make README more pleasant to read Matthieu Moy
2016-02-23 17:40 ` [PATCH 1/5] README: use markdown syntax Matthieu Moy
2016-02-23 19:07   ` Junio C Hamano [this message]
2016-02-23 19:50     ` Matthieu Moy
2016-02-24  7:08     ` Johannes Schindelin
2016-02-24 10:18       ` Jeff King
2016-02-23 17:40 ` [PATCH 2/5] README.md: add hyperlinks on filenames Matthieu Moy
2016-02-23 19:10   ` Junio C Hamano
2016-02-23 19:52     ` Matthieu Moy
2016-02-23 17:40 ` [PATCH 3/5] README.md: move the link to git-scm.com up Matthieu Moy
2016-02-23 17:40 ` [PATCH 4/5] README.md: don't call git stupid in the title Matthieu Moy
2016-02-23 19:13   ` Junio C Hamano
2016-02-23 20:51     ` Matthieu Moy
2016-02-23 21:37       ` Junio C Hamano
2016-02-23 17:40 ` [PATCH 5/5] README.md: move down historical explanation about the name Matthieu Moy
2016-02-24 10:22 ` [RFC/PATCH 0/5] Make README more pleasant to read Jeff King
2016-02-24 13:37   ` Matthieu Moy
2016-02-25  6:14     ` Jeff King
2016-02-25  6:22       ` Junio C Hamano
2016-02-25  8:37 ` [PATCH v2 " Matthieu Moy
2016-02-25  8:37   ` [PATCH v2 1/5] README: use markdown syntax Matthieu Moy
2016-02-25  8:37   ` [PATCH v2 2/5] README.md: add hyperlinks on filenames Matthieu Moy
2016-02-25  8:37   ` [PATCH v2 3/5] README.md: move the link to git-scm.com up Matthieu Moy
2016-02-25  8:37   ` [PATCH v2 4/5] README.md: don't call git stupid in the title Matthieu Moy
2016-02-25  8:37   ` [PATCH v2 5/5] README.md: move down historical explanation about the name Matthieu Moy

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=xmqqoab71c09.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=Matthieu.Moy@imag.fr \
    --cc=emma.westby@gmail.com \
    --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.
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).