From: Eric Blake <eblake@redhat.com>
To: Pranith Kumar <bobby.prani@gmail.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"Daniel P. Berrange" <berrange@redhat.com>,
John Snow <jsnow@redhat.com>,
"open list:All patches CC here" <qemu-devel@nongnu.org>,
famz@redhat.com, Peter Maydell <peter.maydell@linaro.org>,
Stefan Weil <sw@weilnetz.de>,
Stefan Hajnoczi <stefanha@gmail.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 3/3] Update README to accomodate markdown format
Date: Wed, 20 Jul 2016 15:41:27 -0600 [thread overview]
Message-ID: <578FF007.8050303@redhat.com> (raw)
In-Reply-To: <CAJhHMCCYjQe-18oUh44B6NzEQXsSSCLQBjmEmWqh5XFMtgPU_w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 718 bytes --]
On 07/20/2016 03:33 PM, Pranith Kumar wrote:
>>> + - http://qemu-project.org/Contribute/StartHere
>>> \ No newline at end of file
>>
>> Why no ending newline?
>>
>
> Hmm, the original README did not have an explicit new line at end of
> file. I am not sure if it is really necessary though. Why do we need
> one?
Technically, ALL text files should have an ending newline. POSIX says
that a file without an ending newline is not a text file, at which point
programs like sed and grep are allowed to do rather interesting things
(such as refuse to process the file because it is binary).
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2016-07-20 21:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 19:39 [Qemu-devel] [PATCH 0/3] Fix regression caused my moving README Pranith Kumar
2016-07-20 19:39 ` [Qemu-devel] [PATCH 1/3] Revert e4dfc5e8e("Move README to markdown") Pranith Kumar
2016-07-20 20:14 ` Stefan Weil
2016-07-20 19:39 ` [Qemu-devel] [PATCH 2/3] Create README.md as a symlink to README Pranith Kumar
2016-07-20 19:39 ` [Qemu-devel] [PATCH 3/3] Update README to accomodate markdown format Pranith Kumar
2016-07-20 20:10 ` Stefan Weil
2016-07-20 20:21 ` Pranith Kumar
2016-07-20 21:29 ` Eric Blake
2016-07-20 21:33 ` Pranith Kumar
2016-07-20 21:41 ` Eric Blake [this message]
2016-07-20 22:07 ` Peter Maydell
2016-07-20 22:15 ` Pranith Kumar
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=578FF007.8050303@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=bobby.prani@gmail.com \
--cc=famz@redhat.com \
--cc=jsnow@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.com \
--cc=sw@weilnetz.de \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.