git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grzegorz Kossakowski <grek@tuffmail.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: 4jxDQ6FQee2H@dyweni.com, spearce@spearce.org, git@vger.kernel.org
Subject: Re: Bug in Git-Gui - Creates corrupt patch
Date: Mon, 02 Mar 2009 15:34:20 +0100	[thread overview]
Message-ID: <49ABEE6C.3000500@tuffmail.com> (raw)
In-Reply-To: <49A567C9.5050203@viscovery.net>

Johannes Sixt pisze:
> 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

I've just stumpled across this problem. Does above imply that reported problem is not considered as a bug?

If so I believe that git gui should enforce new lines at the end of a file or at least provide more meaningful error msg.

-- 
Best regards,
Grzegorz Kossakowski

  parent reply	other threads:[~2009-03-02 14:36 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
2009-02-25 16:24     ` 4jxDQ6FQee2H
2009-03-02 14:34   ` Grzegorz Kossakowski [this message]
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=49ABEE6C.3000500@tuffmail.com \
    --to=grek@tuffmail.com \
    --cc=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).