From: Lucian Smith <lucianoelsmitho@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: git-svn bridge and line endings
Date: Tue, 23 Aug 2016 10:31:23 -0700 [thread overview]
Message-ID: <CAHLmBr3+3WccbYTm1v2_jd+hR6rygJQfPtH6+MMP-xPLjEy72w@mail.gmail.com> (raw)
In-Reply-To: <xmqqh9abwg4j.fsf@gitster.mtv.corp.google.com>
Windows doesn't have any problem reading files with any form of crlf.
The main issue we have run into thus far is that if I create a new
file in Windows, it's going to have crlf, and if I check it in that
way through this svn process, the file is then stored with crlfs,
which git does not expect. A wide variety of problems results.
-Lucian
On Tue, Aug 23, 2016 at 10:26 AM, Junio C Hamano <gitster@pobox.com> wrote:
> Lucian Smith <lucianoelsmitho@gmail.com> writes:
>
>> The setup is that we have a git repository on github, and I've checked
>> out a branch on my Windows machine using Tortoise svn. I make
>> changes, commit them, and the branch is updated. In general, this
>> works fine.
>
> Hmph, doesn't Windows port ship with core.autocrlf these days?
prev parent reply other threads:[~2016-08-23 17:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAHLmBr2CRzt58RB+_YmnXcyost-R5=Ff51tALf1xh0kGk+frDw@mail.gmail.com>
2016-08-23 0:04 ` git-svn bridge and line endings Lucian Smith
2016-08-23 3:07 ` Eric Wong
2016-08-23 4:58 ` Alfred Perlstein
2016-08-23 5:54 ` Eric Wong
2016-08-23 16:14 ` Lucian Smith
2016-08-23 17:36 ` Julian Phillips
2016-08-23 17:50 ` Lucian Smith
2016-08-23 19:07 ` Torsten Bögershausen
2016-08-23 16:43 ` Torsten Bögershausen
2016-08-23 17:08 ` Lucian Smith
2016-08-23 17:26 ` Junio C Hamano
2016-08-23 17:31 ` Lucian Smith [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAHLmBr3+3WccbYTm1v2_jd+hR6rygJQfPtH6+MMP-xPLjEy72w@mail.gmail.com \
--to=lucianoelsmitho@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).