git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 1/5] README: use markdown syntax

From
Johannes Schindelin <johannes.schindelin@gmx.de>
Date
Feb 24, 2016, 07:08 UTC
Message-ID
<alpine.DEB.2.20.1602240801550.3152@virtualbox>
In-Reply-To
<xmqqoab71c09.fsf@gitster.mtv.corp.google.com>
Hi Junio,
On Tue, 23 Feb 2016, Junio C Hamano wrote:
Show 14 quoted lines
> 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.

That assumes that the primary audience of the README file is the developers who already decided to clone the repository, as opposed to people browsing the README file in the browser to determine whether they found the correct project, or to read up on the background of the project without downloading the entire source code.

I'd wager real money (without scientific evidence. just going on common sense) that your 'less' people are in the vast minority.

Since I am convinced that markdown'ed READMEs enhance the user experience dramatically, Git for Windows has one already for a long time.

Hence *my* main objection: this patch series would conflict with patches we carry in Git for Windows.

;-)

Ciao, Dscho

P.S.: If it was not clear, my objection was meant as a joke. I am very much in favor of enhancing the user experience via Matthieu's patches.

Previous: Matthieu MoyNext: Jeff King
Message 5 of 25 in “Make README more pleasant to read”
  1. 0/5 Make README more pleasant to readMatthieu Moy, Feb 23, 2016
  2. 1/5 README: use markdown syntaxMatthieu Moy, Feb 23, 2016
  3. Junio C HamanoFeb 23, 2016
  4. Matthieu MoyFeb 23, 2016
  5. Johannes SchindelinFeb 24, 2016
  6. Jeff KingFeb 24, 2016
  7. 2/5 README.md: add hyperlinks on filenamesMatthieu Moy, Feb 23, 2016
  8. Junio C HamanoFeb 23, 2016
  9. Matthieu MoyFeb 23, 2016
  10. 3/5 README.md: move the link to git-scm.com upMatthieu Moy, Feb 23, 2016
  11. 4/5 README.md: don't call git stupid in the titleMatthieu Moy, Feb 23, 2016
  12. Junio C HamanoFeb 23, 2016
  13. Matthieu MoyFeb 23, 2016
  14. Junio C HamanoFeb 23, 2016
  15. 5/5 README.md: move down historical explanation about the nameMatthieu Moy, Feb 23, 2016
  16. Jeff KingFeb 24, 2016
  17. Matthieu MoyFeb 24, 2016
  18. Jeff KingFeb 25, 2016
  19. Junio C HamanoFeb 25, 2016
  20. 0/5 Make README more pleasant to readMatthieu Moy, Feb 25, 2016
  21. 1/5 README: use markdown syntaxMatthieu Moy, Feb 25, 2016
  22. 2/5 README.md: add hyperlinks on filenamesMatthieu Moy, Feb 25, 2016
  23. 3/5 README.md: move the link to git-scm.com upMatthieu Moy, Feb 25, 2016
  24. 4/5 README.md: don't call git stupid in the titleMatthieu Moy, Feb 25, 2016
  25. 5/5 README.md: move down historical explanation about the nameMatthieu Moy, Feb 25, 2016

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.