All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Jesper Juhl <jj@chaosbits.net>
Cc: alsa-devel@alsa-project.org, Andiry Xu <andiry.xu@amd.com>,
	linux-doc@vger.kernel.org, Takashi Iwai <tiwai@suse.de>,
	kjsisson@bellsouth.net, Randy Dunlap <rdunlap@xenotime.net>,
	Sarah Sharp <sarah.a.sharp@linux.intel.com>,
	linux-media@vger.kernel.org, Andy Lutomirski <luto@mit.edu>,
	Mike Frysinger <vapier@gentoo.org>,
	Josua Dietze <digidietze@draisberghof.de>,
	Michael Hennerich <michael.hennerich@analog.com>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	Ben Dooks <ben-linux@fluff.org>, Matthew Garrett <mjg@redhat.com>,
	trivial@kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, Ben Dooks <ben@simtec.co.uk>,
	Andrew Morton <akpm@linux-foundation.org>,
	"H. Peter Anvin" <hpa@linux.intel.com>
Subject: Re: [PATCH] [Trivial] Documentation: Add newline at end-of-file to files lacking one
Date: Tue, 17 Apr 2012 13:03:35 -0300	[thread overview]
Message-ID: <4F8D9457.2080900@redhat.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1204162329190.21898@swampdragon.chaosbits.net>

Em 16-04-2012 18:35, Jesper Juhl escreveu:
> This patch simply adds a newline character at end-of-file to those
> files in Documentation/ that currently lack one.
> 
> This is done for a few different reasons:
> 
> A) It's rather annoying when you do "cat some_file.txt" that your
>    prompt/cursor ends up at the end of the last line of output rather
>    than on a new line.
> 
> B) Some tools that process files line-by-line may get confused by the
>    lack of a newline on the last line.
> 
> C) The "\ No newline at end of file" line in diffs annoys me for some
>    reason.
> 
> So, let's just add the missing newline once and for all.
> 
> Signed-off-by: Jesper Juhl <jj@chaosbits.net>
> ---

>  Documentation/dvb/opera-firmware.txt                           |    2 +-
>  Documentation/video4linux/cpia2_overview.txt                   |    2 +-
>  Documentation/video4linux/stv680.txt                           |    2 +-

Acked-by: Mauro Carvalho Chehab <mchehab@redhat.com>

WARNING: multiple messages have this Message-ID (diff)
From: Mauro Carvalho Chehab <mchehab@redhat.com>
To: Jesper Juhl <jj@chaosbits.net>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
	Randy Dunlap <rdunlap@xenotime.net>,
	trivial@kernel.org, kjsisson@bellsouth.net,
	Ben Dooks <ben-linux@fluff.org>,
	Mauro Carvalho Chehab <mchehab@infradead.org>,
	Ben Dooks <ben@simtec.co.uk>, Jaroslav Kysela <perex@perex.cz>,
	Takashi Iwai <tiwai@suse.de>, Andy Lutomirski <luto@mit.edu>,
	"H. Peter Anvin" <hpa@linux.intel.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Josua Dietze <digidietze@draisberghof.de>,
	Andiry Xu <andiry.xu@amd.com>, Matthew Garrett <mjg@redhat.com>,
	Sarah Sharp <sarah.a.sharp@linux.intel.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Mike Frysinger <vapier@gentoo.org>,
	Michael Hennerich <michael.hennerich@analog.com>,
	linux-media@vger.kernel.org, alsa-devel@alsa-project.org
Subject: Re: [PATCH] [Trivial] Documentation: Add newline at end-of-file to files lacking one
Date: Tue, 17 Apr 2012 13:03:35 -0300	[thread overview]
Message-ID: <4F8D9457.2080900@redhat.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1204162329190.21898@swampdragon.chaosbits.net>

Em 16-04-2012 18:35, Jesper Juhl escreveu:
> This patch simply adds a newline character at end-of-file to those
> files in Documentation/ that currently lack one.
> 
> This is done for a few different reasons:
> 
> A) It's rather annoying when you do "cat some_file.txt" that your
>    prompt/cursor ends up at the end of the last line of output rather
>    than on a new line.
> 
> B) Some tools that process files line-by-line may get confused by the
>    lack of a newline on the last line.
> 
> C) The "\ No newline at end of file" line in diffs annoys me for some
>    reason.
> 
> So, let's just add the missing newline once and for all.
> 
> Signed-off-by: Jesper Juhl <jj@chaosbits.net>
> ---

>  Documentation/dvb/opera-firmware.txt                           |    2 +-
>  Documentation/video4linux/cpia2_overview.txt                   |    2 +-
>  Documentation/video4linux/stv680.txt                           |    2 +-

Acked-by: Mauro Carvalho Chehab <mchehab@redhat.com>

  parent reply	other threads:[~2012-04-17 16:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-16 21:35 [PATCH] [Trivial] Documentation: Add newline at end-of-file to files lacking one Jesper Juhl
2012-04-17 15:41 ` Rob Landley
2012-04-17 16:03 ` Mauro Carvalho Chehab [this message]
2012-04-17 16:03   ` Mauro Carvalho Chehab

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=4F8D9457.2080900@redhat.com \
    --to=mchehab@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=andiry.xu@amd.com \
    --cc=ben-linux@fluff.org \
    --cc=ben@simtec.co.uk \
    --cc=digidietze@draisberghof.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=hpa@linux.intel.com \
    --cc=jj@chaosbits.net \
    --cc=kjsisson@bellsouth.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=luto@mit.edu \
    --cc=mchehab@infradead.org \
    --cc=michael.hennerich@analog.com \
    --cc=mjg@redhat.com \
    --cc=rdunlap@xenotime.net \
    --cc=sarah.a.sharp@linux.intel.com \
    --cc=tiwai@suse.de \
    --cc=trivial@kernel.org \
    --cc=vapier@gentoo.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.
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.