From: "Dmitry Kakurin" <dmitry.kakurin@gmail.com>
To: "Steffen Prohaska" <prohaska@zib.de>
Cc: "Marius Storm-Olsen" <marius@trolltech.com>,
"Junio C Hamano" <gitster@pobox.com>,
"Git Mailing List" <git@vger.kernel.org>,
"Brian Downing" <bdowning@lavos.net>,
"Johannes Schindelin" <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH 2/2] checkout: fix attribute handling in checkout all
Date: Mon, 13 Aug 2007 07:35:40 -0700 [thread overview]
Message-ID: <a1bbc6950708130735g73508d1ev2114cea3612d77c9@mail.gmail.com> (raw)
In-Reply-To: <DD0F51D8-390E-41DB-BD80-0BB440418D01@zib.de>
On 8/13/07, Steffen Prohaska <prohaska@zib.de> wrote:
> My target audience of Git on Windows are Windows users and, frankly,
> that is the only reasonable way to think about Windows. Why else should
> I boot Windows, if I don't have real Windows users in mind? I mean,
> Windows is not the superior platform to build Unix on top. The reason
> to boot Windows is Windows itself, including its real users.
I agree with this approach.
> Maybe I don't fully understand what msysgit is about. I thought it would
> be about real Windows support, which I think requires to accept what
> Windows users expect to be the right thing: Windows EOL.
msysgit is Build Environment for Git on Windows. It's purpose is to
facilitate Git development. This is not what end-user wants.
Another installer (WinGit) is targeting end users. It is just so
happens that msysgit is in better shape right now and more useful. But
long term it will not be the case.
Here is another consideration: let's say I've started a new git repo
under Windows with no autocrlf set. Then my repo will contain crlf
line endings.
Now let's say that someone else checks out this repo with
autocrlf=true. What would happen then? Will they get cr cr lf?
--
- Dmitry
next prev parent reply other threads:[~2007-08-13 14:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-12 20:34 [PATCH 1/2] attr: fix attribute handling if .gitattributes is involved Steffen Prohaska
2007-08-12 20:34 ` [PATCH 2/2] checkout: fix attribute handling in checkout all Steffen Prohaska
2007-08-12 21:50 ` Junio C Hamano
2007-08-12 22:26 ` Steffen Prohaska
2007-08-13 6:14 ` Junio C Hamano
2007-08-13 6:32 ` Marius Storm-Olsen
2007-08-13 6:50 ` Steffen Prohaska
2007-08-13 7:15 ` Marius Storm-Olsen
2007-08-13 7:32 ` Steffen Prohaska
2007-08-13 8:39 ` Marius Storm-Olsen
2007-08-13 8:51 ` Steffen Prohaska
2007-08-13 14:35 ` Dmitry Kakurin [this message]
2007-08-14 8:40 ` [PATCH 1/2] attr.c: refactoring Junio C Hamano
2007-08-14 8:41 ` [PATCH 2/2] attr.c: read .gitattributes from index as well Junio C Hamano
2007-08-13 6:46 ` [PATCH 2/2] checkout: fix attribute handling in checkout all Steffen Prohaska
2007-08-13 16:14 ` Johannes Schindelin
2007-08-13 7:24 ` David Kastrup
2007-08-13 14:55 ` git-update-ref bug? (was: [PATCH 2/2] checkout: fix attribute handling in checkout all) David Kastrup
2007-08-13 20:12 ` [PATCH 2/2] checkout: fix attribute handling in checkout all Junio C Hamano
2007-08-13 1:51 ` [PATCH 1/2] attr: fix attribute handling if .gitattributes is involved Brian Downing
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=a1bbc6950708130735g73508d1ev2114cea3612d77c9@mail.gmail.com \
--to=dmitry.kakurin@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=bdowning@lavos.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=marius@trolltech.com \
--cc=prohaska@zib.de \
/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).