From: "Peter Eriksen" <s022018@student.dtu.dk>
To: git@vger.kernel.org
Subject: Problems with binary patches (pull) and spaces in filenames (gitk)
Date: Wed, 9 Nov 2005 22:37:30 +0100 [thread overview]
Message-ID: <20051109213730.GA23052@ebar091.ebar.dtu.dk> (raw)
Hello,
I've got a nice project, where I am tracking both binary files and
filenames with spaces. So, I've noticed two small cosmetic bugs:
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
2) When there are spaces in filenames, gitk only shows the first part of
the name in the filelist at the buttom right.
Regards,
Peter
next reply other threads:[~2005-11-09 21:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-09 21:37 Peter Eriksen [this message]
2005-11-09 22:09 ` Problems with binary patches (pull) and spaces in filenames (gitk) Junio C Hamano
2005-11-09 22:36 ` Junio C Hamano
2005-11-09 23:33 ` Peter Eriksen
2005-11-09 23:00 ` Jan Harkes
2005-11-09 22:10 ` Linus Torvalds
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=20051109213730.GA23052@ebar091.ebar.dtu.dk \
--to=s022018@student.dtu.dk \
--cc=git@vger.kernel.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