public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin@cygwin.com
Subject: Re: GitForWindows vs. Cygwin
Date: Wed, 21 Mar 2018 18:47:00 -0000	[thread overview]
Message-ID: <87fu4tff1m.fsf@Rainer.invalid> (raw)
In-Reply-To: <587wcTwzy5968Set.1521586344@web02.cms.usa.net> (KARL BOTTS's	message of "Tue, 20 Mar 2018 17:52:24 -0500")

KARL BOTTS writes:
> 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.

As long as you keep the program versions reasonably up-to-date
w.r.t. each other and have a strict policy about CRLF handling in place
things should work OK.  You also need to worry more about having
sensible ACL on the repositories and keeping them sane.  Mixing these
two (POSIX vs. Windows way of things) does give you more rope to
entangle yourself in, so you need to know what you're doing when you
veer off the well-trodden path.  It helps to test a few things on
something easily discardable before you have a go at production repos.


Regards,
Achim.
-- 
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+

Factory and User Sound Singles for Waldorf Q+, Q and microQ:
http://Synth.Stromeko.net/Downloads.html#WaldorfSounds

--
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 18:40 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
2018-03-21 18:47 ` Achim Gratz [this message]
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=87fu4tff1m.fsf@Rainer.invalid \
    --to=stromeko@nexgo.de \
    --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).