From: "Peter B." <tripleshiftone@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Bug with Cygwin's 'quilt' is actually in 'patch'
Date: Wed, 03 Jul 2013 15:35:00 -0000 [thread overview]
Message-ID: <51D4445D.6090909@email.com> (raw)
In-Reply-To: <20130703133048.GG5118@calimero.vinschen.de>
On 03.07.2013 15:30 Corinna Vinschen wrote:
> On Jul 3 15:04, Peter B. wrote:
>> On 03.07.2013 14:33 Corinna Vinschen wrote:
>>> On Jul 3 05:03, Peter B. wrote:
>>>> On Jun 20 09:46, Corinna Vinschen wrote:
>>>>> I'll build a new patch 2.7.1 for 32 bit today. I hope that fixes it
>>>>> for 32 bit as well.
>>>> The new 2.7.1 (32bit) brakes CRLF handling for me completely. The old
>>>> 2.6.1 works properly. 2.7.1 with text files converted from CRLF to LF
>>>> works properly as well.
>>>>
>>>> Can you take a look at the download link below? It includes an example
>>>> file (with CRLF), the corresponding patch (LF) and the two binaries
>>>> (patch v2.6.1 and v2.7.1).
>>>>
>>>> http://www60.zippyshare.com/v/13352963/file.html
>>> Please provide a direct link which doesn't require to enable scripting
>>> in a web browser to download.
>>>
>>>
>>> Thanks,
>>> Corinna
>>>
>> Please download this picture (jpg) and rename the file suffix to 7z or
>> open with corresponding archiver directly.
>>
>> http://abload.de/img/patchfus75.jpg (99KB)
> Thanks. The behaviour here is a deliberate upstream choice to apply the
> patch only if the line endings are the same as in the file to patch.
>
> If you really must apply non-CRLF patches to CRLF files, consider using
> a temporary text mount:
> http://cygwin.com/cygwin-ug-net/using-utils.html#mount
>
>
> Corinna
>
Sounds like intended behavior. I will try to tackle the problem
otherwise then.
The culprit here is the JavaVM that produces different
EOLs on different platforms (running a binary decompiler -> txt).
Thanks.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2013-07-03 15:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 3:05 Peter B.
2013-07-03 12:33 ` Corinna Vinschen
2013-07-03 13:07 ` Peter B.
2013-07-03 13:30 ` Corinna Vinschen
2013-07-03 15:35 ` Peter B. [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-06-18 5:37 Bug with Cygwin's 'quilt' Matt D.
2013-06-18 5:47 ` Matt D.
2013-06-20 5:47 ` Bug with Cygwin's 'quilt' is actually in 'patch' Matt D.
2013-06-20 6:35 ` Christopher Faylor
2013-06-20 7:44 ` Matt D.
2013-06-20 8:22 ` Corinna Vinschen
2013-06-21 12:15 ` Corinna Vinschen
2013-06-21 17:06 ` Matt D.
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=51D4445D.6090909@email.com \
--to=tripleshiftone@gmail.com \
--cc=cygwin@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).