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

Re: Problems with binary patches (pull) and spaces in filenames (gitk)

From
Junio C Hamano <junkio@cox.net>
Date
Nov 9, 2005, 22:09 UTC
Message-ID
<7vfyq5bhi2.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20051109213730.GA23052@ebar091.ebar.dtu.dk>
"Peter Eriksen" <s022018@student.dtu.dk> writes:
Show 8 quoted lines
> 1) When pulling an updated binary files, I guess it still tries to 
>    print this update summary by making and processing patches, and so
>    gives this error:
>
>        Updating from ab1c4033ba98c043e13da3446e7f244ac7f79942 to
>        c164231f6b59fd80171e95f31d762a80d884c708.
>        Fast forward
>        fatal: patch with only garbage at line 3249

Hmm. Perhaps a suboption to git-apply --stat to tell it not to barf is helpful? In the meantime, could you pull with -n flag?

> 2) When there are spaces in filenames, gitk only shows the first part of
>    the name in the filelist at the buttom right.

Another minor gitk gripe I have is that it does not look at subdirectories of refs/{heads,tags}/ so I do not get labels to my topic branch heads.

Previous: Peter EriksenNext: Junio C Hamano
Message 2 of 6 in “Problems with binary patches (pull) and spaces in filenames (gitk)”
  1. Peter EriksenNov 9, 2005
  2. Junio C HamanoNov 9, 2005
  3. Junio C HamanoNov 9, 2005
  4. Peter EriksenNov 9, 2005
  5. Jan HarkesNov 9, 2005
  6. Linus TorvaldsNov 9, 2005

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.