public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Gene Pavlovsky <gene.pavlovsky@gmail.com>
To: cygwin@cygwin.com
Subject: Re: TortoiseGit + Cygwin git: unified diff fails (cygheap read copy failed)
Date: Thu, 17 Nov 2016 14:00:00 -0000	[thread overview]
Message-ID: <CAPTiy3P5Z68Sj326XG3S0DDsMFGqpDQBcJV7qqtGkxM7q2eLpg@mail.gmail.com> (raw)
In-Reply-To: <CAEhDDbB2=3F4xwgA7gg76WFw7+q7A=Wn-i866WGnZS-WgAyetQ@mail.gmail.com>

>> I'm using TortoiseGit with Cygwin git (Cygwin workarounds enabled in
>> advanced TortoiseGit settings). For the most part, everything works
>> correctly.
>
> Although this is probably unrelated, I've had problems with
> TortoiseSVN and Cygwin's svn (not Git), because Tortoise uses DOS line
> endings (\r\n) whereas Cygwin programs use Unix line endings (\n).

TortoiseGit doesn't seem to have line endings-related problems (in
general), but who knows, maybe they missed a spot...
I'll post this issue to TortoiseGit's bug tracker. I wonder if anybody
else is using TortoiseGit with Cygwin's git and "Show changes as
unified diff" in TortoiseGit's log work for them?

--
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

  reply	other threads:[~2016-11-17 12:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-17  3:37 Gene Pavlovsky
2016-11-17 13:30 ` Csaba Raduly
2016-11-17 14:00   ` Gene Pavlovsky [this message]
2016-11-20 16:42 ` Gene Pavlovsky

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=CAPTiy3P5Z68Sj326XG3S0DDsMFGqpDQBcJV7qqtGkxM7q2eLpg@mail.gmail.com \
    --to=gene.pavlovsky@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).