On Wed, Feb 24, 2016 at 08:08:52AM +0100, Johannes Schindelin wrote:
> > 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
Hi Junio,
On Tue, 23 Feb 2016, Junio C Hamano wrote:
> Matthieu Moy writes:
>
> > This allows repository browsers like GitHub to display the content of
> > the file nicely formatted.
> >
> > Signed-off-by: Matthieu Moy
> > ---
>
> To be honest, I have the most problem with this step in the wh
Junio C Hamano writes:
> Matthieu Moy writes:
>
>> This allows repository browsers like GitHub to display the content of
>> the file nicely formatted.
>>
>> Signed-off-by: Matthieu Moy
>> ---
>
> To be honest, I have the most problem with this step in the whole
> series.
>
> Markdown when rende
Matthieu Moy writes:
> This allows repository browsers like GitHub to display the content of
> the file nicely formatted.
>
> Signed-off-by: Matthieu Moy
> ---
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
This allows repository browsers like GitHub to display the content of
the file nicely formatted.
Signed-off-by: Matthieu Moy
---
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/R
5 matches
Mail list logo