From: "Torsten Bögershausen" <tboegi@web.de>
To: Piotr Krukowiecki <piotr.krukowiecki@gmail.com>, git@vger.kernel.org
Subject: Re: EOL handling (EGit/svn/Windows)
Date: Tue, 10 Feb 2015 06:49:33 +0100 [thread overview]
Message-ID: <54D99BED.8010005@web.de> (raw)
In-Reply-To: <CAA01Csrp0ZOouM5zhVuHQW9sWCnbMMLRkmcbRtgsU3k8wNtSqw@mail.gmail.com>
On 02/09/2015 11:22 PM, Piotr Krukowiecki wrote:
>Any other suggestions?
My, somewhat personally, suggestion:
If there is more than one developer, don't use core.autocrlf at all-
it is a local setting, which doesn't travel through the repo, and
is slightly different in Git Egit, depending on the version.
Git for Windows has it enabled by default, Cygwin has not.
Which Git versions are you using ?
How many people are there involved, how many on Windows, how many on Linux ?
Do you want to commit to svn, or is this a one-time conversion ?
If it is a one-time conversion, and you continue to work in Git only,
then the cleanest, most portable and future proof way is to use the
.gitattributes file,
add that to the repo, do the normalization and push.
A line like this:
* text=auto
is the easiest way.
Have a look at
https://www.kernel.org/pub/software/scm/git/docs/gitattributes.html
take a tee or coffee, do some experiments first with a dummy repo,
but all the client OS/Gits involved.
Please let us know the result (or feel free to ask more questions)
next prev parent reply other threads:[~2015-02-10 5:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-09 22:22 EOL handling (EGit/svn/Windows) Piotr Krukowiecki
2015-02-10 5:49 ` Torsten Bögershausen [this message]
2015-02-10 10:52 ` Piotr Krukowiecki
2015-02-10 15:32 ` Torsten Bögershausen
2015-02-11 11:46 ` Piotr Krukowiecki
2015-02-11 15:51 ` Piotr Krukowiecki
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=54D99BED.8010005@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=piotr.krukowiecki@gmail.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 NNTP newsgroup(s).