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

Re: Bug in Git-Gui - Creates corrupt patch

From
44jxdq6fqee2h@dyweni.com <4jxdq6fqee2h@dyweni.com>
Date
Feb 25, 2009, 16:24 UTC
Message-ID
<20090225102453.38d993ce@family.dyweni.com>
In-Reply-To
<20090225101037.104b48a1@family.dyweni.com>

In case anyone else is facing this same situation, a simple script like this did the trick for me:

------------------------------------------------ #!/bin/bash

find ./ -type f | grep -v .git | while read filename
do
	last=$(
		tail -c 1 "$filename" | 
		od -x | 
		head -n 1 | 
		awk '{ print $2 }'
	)
	
	if [ "x$last" != "x000a" ]
	then
		echo >> "$filename"
	fi
done
------------------------------------------------
Show 33 quoted lines
> <4jxDQ6FQee2H@dyweni.com> wrote:
> 
> 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
Previous: 4jxdq6fqee2h@dyweni.comNext: Grzegorz Kossakowski
Message 5 of 7 in “Bug in Git-Gui - Creates corrupt patch”
  1. 4jxdq6fqee2h@dyweni.comFeb 25, 2009
  2. 4jxdq6fqee2h@dyweni.comFeb 25, 2009
  3. Johannes SixtFeb 25, 2009
  4. 4jxdq6fqee2h@dyweni.comFeb 25, 2009
  5. 4jxdq6fqee2h@dyweni.comFeb 25, 2009
  6. Grzegorz KossakowskiMar 2, 2009
  7. Johannes SixtMar 2, 2009

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.