From: Junio C Hamano <gitster@pobox.com>
To: Chris B <chris.blaszczynski@gmail.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Erik Faye-Lund <kusmabite@gmail.com>,
git@vger.kernel.org, msysgit@googlegroups.com
Subject: Re: Re: Git for Windows and line endings
Date: Fri, 19 Oct 2012 10:22:08 -0700 [thread overview]
Message-ID: <7vlif2js1r.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CADKp0pxuFsSEeZoeemyaqhSJEcsjj1arEOsF4Ub8=76y7tkwHg@mail.gmail.com> (Chris B.'s message of "Fri, 19 Oct 2012 10:39:27 -0400")
Chris B <chris.blaszczynski@gmail.com> writes:
> - If there was SO MUCH thought into this, then it was too much...
I do not have much to add to what area experts already said on bits
specific to Git for Windows, but on just this part:
> - Our builds were not breaking, it was production due to deployment
> model utilizing Git. What if there was a process to extract from Git
> and then distribute?
Do you mean something like "git archive"? Or do you have something
else in mind?
> - Developers are not expecting revision control system to make changes
> to files they commit.
But isn't there a distinction between the logical content and its
physical representation? In source code (that is what developers
use a source code management system for), especially those of
cross-platform projects, the logical lines end with LF and physical
lines end with whatever is convenient on the platform of each
participant of the project. There needs a way to convert between
the two.
It does not sound fair to call it a crime if the port to a platform,
whose users (at least the majority of them) expect the latter to be
CRLF, chose to default to that to help the majority, as long as
there are ways for the minority power users to choose to use LF in
the physical representation on their working trees.
--
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.
You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en
next prev parent reply other threads:[~2012-10-19 17:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 22:13 Git for Windows and line endings Chris B
2012-10-18 22:40 ` Erik Faye-Lund
2012-10-19 6:09 ` Johannes Schindelin
2012-10-19 14:39 ` [msysGit] " Chris B
2012-10-19 17:22 ` Junio C Hamano [this message]
2012-10-19 20:59 ` Jeff King
2012-10-19 21:53 ` [msysGit] " John Szakmeister
2012-11-04 12:37 ` Raja R Harinath
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=7vlif2js1r.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=chris.blaszczynski@gmail.com \
--cc=git@vger.kernel.org \
--cc=kusmabite@gmail.com \
--cc=msysgit@googlegroups.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).