git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: <4jxDQ6FQee2H@dyweni.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: git@vger.kernel.org, spearce@spearce.org
Subject: Re: Bug in Git-Gui - Creates corrupt patch
Date: Wed, 25 Feb 2009 10:10:37 -0600	[thread overview]
Message-ID: <20090225101037.104b48a1@family.dyweni.com> (raw)
In-Reply-To: <49A567C9.5050203@viscovery.net>

Hannes / List,

Thank you for the advise on "\ No newline at end of file".

I have almost 4,000 files that are formatted with "\ No newline at end
of file".  Does anyone know of an easy way to re-format my files so
that they have a newline at the end?

The files in question are PHP files that are dynamically included, so I
want to prevent arbitrary spaces from showing up in the rendered pages.

I'm running Linux.  A bash or perl script would be preferable, but
anything will suffice.

Thanks!


> Johannes Sixt <j.sixt@viscovery.net> wrote:
>
> 4jxDQ6FQee2H@dyweni.com schrieb:
> > 3. Using git-gui, try to stage *only* the last line marked for
> > removal (should be '-	}').
> > 
> > I get 'fatal: corrupt patch at line 22'.  
> 
> "Stage/Unstage line" does not work for files that have
> 
> \ No newline at end of file
> 
> -- Hannes
> 

  reply	other threads:[~2009-02-25 16:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-25 15:03 Bug in Git-Gui - Creates corrupt patch 4jxDQ6FQee2H
2009-02-25 15:26 ` 4jxDQ6FQee2H
2009-02-25 15:46 ` Johannes Sixt
2009-02-25 16:10   ` 4jxDQ6FQee2H [this message]
2009-02-25 16:24     ` 4jxDQ6FQee2H
2009-03-02 14:34   ` Grzegorz Kossakowski
2009-03-02 14:39     ` Johannes Sixt

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=20090225101037.104b48a1@family.dyweni.com \
    --to=4jxdq6fqee2h@dyweni.com \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.net \
    --cc=spearce@spearce.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 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 NNTP newsgroup(s).