From: "Alexander Gladysh" <agladysh@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git-users@googlegroups.com, git@vger.kernel.org
Subject: Re: Git Gui does not want to work on chunk level
Date: Thu, 4 Sep 2008 13:20:21 +0400 [thread overview]
Message-ID: <c6c947f60809040220t589e65bfkbd693fd335792069@mail.gmail.com> (raw)
In-Reply-To: <20080903230814.GJ28315@spearce.org>
On Thu, Sep 4, 2008 at 3:08 AM, Shawn O. Pearce <spearce@spearce.org> wrote:
> Alexander Gladysh <agladysh@gmail.com> wrote:
>> On Wed, Aug 27, 2008 at 1:16 PM, Alexander Gladysh <agladysh@gmail.com> wrote:
>> > I like 'stage hunk for commit' feature in Git Gui, but often it gives
>> > me an error message box:
>> >
>> > fatal: git-apply: bad git-diff - inconsistent old filename on line 4
> ...
> I've never seen that before, but its clearly dumping a bad diff
> into git-apply.
>
> Open up lib/diff.tcl and find "proc apply_hunk". Inside of the
> catch maybe insert a puts to see the diff, e.g.:
> <...>
> Then if you can scrub the context and +/- lines for a bad diff and
> send us at least the headers, or tell us how they are malformed,
> it would help to debug it.
Thank you!
Header looks well-formed to me:
diff --git a/path/file.ext b/path/file.ext
--- a/path/file.ext
+++ b/path/file.ext
I have sent you full output privately. I do not see anything unusual
in it... Anyplace where I may put more logging?
Thanks again,
Alexander.
next prev parent reply other threads:[~2008-09-04 9:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c6c947f60808270216k2feb8f9ar765cdee1fc3910ee@mail.gmail.com>
[not found] ` <c6c947f60808270216k2feb8f9ar765cdee1fc3910ee-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-09-03 19:23 ` Git Gui does not want to work on chunk level Alexander Gladysh
2008-09-03 23:08 ` Shawn O. Pearce
2008-09-04 9:20 ` Alexander Gladysh [this message]
2008-09-04 14:37 ` Shawn O. Pearce
[not found] ` <20080904143723.GB23708-o8xcbExO1WpAfugRpC6u6w@public.gmane.org>
2008-09-04 14:54 ` Alexander Gladysh
2008-09-05 4:53 ` Shawn O. Pearce
2008-09-05 5:18 ` Junio C Hamano
2008-09-05 5:20 ` Shawn O. Pearce
[not found] ` <20080905045327.GA31166-o8xcbExO1WpAfugRpC6u6w@public.gmane.org>
2008-09-05 19:27 ` Alexander Gladysh
2008-09-15 7:08 ` Johannes Sixt
2010-11-30 21:19 ` Bert Wesarg
2010-11-30 22:20 ` Bert Wesarg
2010-12-06 21:30 ` Bert Wesarg
2008-09-15 14:21 ` Alexander Gladysh
[not found] ` <c6c947f60809150721m1ec11f10xc68ce39559398659-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2008-09-15 14:24 ` Shawn O. Pearce
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=c6c947f60809040220t589e65bfkbd693fd335792069@mail.gmail.com \
--to=agladysh@gmail.com \
--cc=git-users@googlegroups.com \
--cc=git@vger.kernel.org \
--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).