public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Frank Fesevur <ffes@users.sourceforge.net>
To: cygwin@cygwin.com
Subject: Re: GitForWindows vs. Cygwin
Date: Wed, 21 Mar 2018 10:28:00 -0000	[thread overview]
Message-ID: <CAKf2h5R7+_GyJVaK5R3pOoOHhYd5FqYvvt=o7Lf=Un2EtOkTYw@mail.gmail.com> (raw)
In-Reply-To: <587wcTwzy5968Set.1521586344@web02.cms.usa.net>

2018-03-20 23:52 GMT+01:00 KARL BOTTS:
> Can anyone enlighten me about the relationship of "Git for Windows" to
> Cygwin?

Depends on how you define "relationship". Tony summed it up very nicely.

> I have no intention to use GFW myself: I use Cygwin git.  But now other people
> around here are discovering GitHub, MSysGit and or GitForWindows.  Pretty
> soon, we are going to wind up with multiple git flavors installed on the same
> host, which worries me.

I use the Cygwin based git tools (tig most of the time) as my main
client, but also use Git for Windows and its tig, WSL based and real
Ubuntu, the builtin git client in Visual Studio and VSCode. I often
combine them in one project, for instance use VS for the simple and
easy commit, use the Cygwin command line for more advance stuff and to
push and pull (because I mainly use SSH).

The **real caveat** is to get your line endings right. You need that
figured out in any multi platform environment, and combining Windows
bases git and Cygwin based git is exactly that. Cygwin and Ubuntu
default to LF. Git for Windows and the VS clients default to CRLF.

We use "git config --global core.autocrlf false" and combine that with
a proper .gitattributes and .editorconfig file. So far that works
quite well for us.

Hope it helps,
Frank

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

  parent reply	other threads:[~2018-03-21  8:54 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20 23:22 KARL BOTTS
2018-03-20 23:50 ` Steven Penny
2018-03-21  0:25 ` Andrey Repin
2018-03-21  4:02   ` Tony Kelman
2018-03-21  4:12     ` Vince Rice
2018-03-21  8:54       ` Thomas Wolff
2018-03-21 14:26         ` cyg Simple
2018-03-21 14:37         ` Vince Rice
2018-03-21 17:36           ` Tony Kelman
2018-03-21 18:11             ` Tony Kelman
2018-03-21 18:40             ` Brian Inglis
2018-03-22 11:37               ` David Macek
2018-03-21 10:28 ` Frank Fesevur [this message]
2018-03-21 18:47 ` Achim Gratz
2018-03-21 23:20   ` Dan Kegel
2018-03-22 16:50 ` R0b0t1

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='CAKf2h5R7+_GyJVaK5R3pOoOHhYd5FqYvvt=o7Lf=Un2EtOkTYw@mail.gmail.com' \
    --to=ffes@users.sourceforge.net \
    --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).