From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Marius Storm-Olsen <marius@trolltech.com>
Cc: Alex Riesen <raa.lkml@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
"Shawn O. Pearce" <spearce@spearce.org>,
Julian Phillips <julian@quantumfyre.co.uk>,
git@vger.kernel.org
Subject: Re: [PATCH 3/3] Teach "git branch" about --new-workdir
Date: Wed, 25 Jul 2007 10:39:14 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707251024390.14781@racer.site> (raw)
In-Reply-To: <46A6F21D.2010306@trolltech.com>
Hi,
On Wed, 25 Jul 2007, Marius Storm-Olsen wrote:
> Alex Riesen said the following on 25.07.2007 01:15:
>
> > I have to stay with Windows, but I'd absolute hate having their stupid
> > line-ending by default. As will my project supervisor, and he gets
> > changes from something like 300 developers. You will definitely get
> > their votes against changing the default
>
> Ok, so maybe not changing the default.
> Though it's weird behavior for _most_ Windows developers out there, I agree
> that the current Windows Git population would mostly prefer the Unix line
> endings. And I can see how someone who's working on Windows and handling a lot
> of patches from other developers of multiple OSs also wanting the
> non-platform-standard Unix line-endings.
Even MacOSX saw the light. More and more tools on Windows (not from M$,
mind you, they still want to lock you in, and I am continually amazed at
the _willingness_ to be locked in!) are behaving sane.
> > Marius said:
> >
> > > I believe, especially at the moment, most Git users on Windows are
> > > mostly developing code in a cross-platform manner, and therefore
> > > care about this problem.
> >
> > Yes. They solve it by working fulltime in \n-lineending. Avoiding that
> > stupid Visual Studio and Notepad helps too.
>
> Huh? You just removed more than 3 _million_[1] potential users.. (Some say 8
> million [2]) Is that a good argument? Why should developers on Windows avoid
> using Windows tools? Because they're 'idiots'? (ref further down in your
> reply)
When somebody does not want the same as you, it comes natural to think of
that person as an idiot. That's psychology, not something rational.
However, I think we are talking about an almost non-issue here: those 3-80
million users "just waiting" for Git probably would not touch it without a
complete installer. And that installer could just ask "which line ending
do you want to suffer through today?"
Which brings _me_ back to my pet hate: why on earth is _no_ one of those
30-800 billion Windows users trying to do something about the lack of a
proper native Windows support for Git? The MinGW port contains commits
from these people (skipping everything that is in official git.git):
Johannes Schindelin
Johannes Sixt
Junio C Hamano
Mark Levedahl
Simon 'corecode' Schubert
I know for certain that the first person, and also the third person, are
not exactly Windows users. I guess not even the last two persons are.
Note that more work has been done on git-gui, because those poor Windows
developers are evidently so uncomfortable with the keyboard that a GUI is
needed. AFAIK only Johannes Sixt and Shawn Pearce worked on the
Windows/git-gui interaction (and again, Shawn is not a Windows user).
Han-Wen made an installer, right, but that installer is lacking bash and
perl, and proper testing, because it was just a proof-of-concept.
Han-Wen is no Windows user either. I tried to pick up on that work, but
unfortunately "gub" (the cross compiling framework he used) is so
Pythonesque that I was put off.
So this leaves me with the question: do Windows users really want a proper
native Windows support for Git? If the answer is yes, why don't they _do_
(as in "not talk") something about it?
(Let me take a BIG, BIIIIIG exception here: Johannes Sixt has worked long
and hard and extremely well on this beast. He is certainly the exception
that proves the rule.)
Ciao,
Dscho
next prev parent reply other threads:[~2007-07-25 9:39 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 18:56 [PATCH 3/3] Teach "git branch" about --new-workdir Johannes Schindelin
2007-07-22 19:16 ` Daniel Barkalow
2007-07-22 19:24 ` Johannes Schindelin
2007-07-22 21:09 ` Julian Phillips
2007-07-22 21:25 ` Johannes Schindelin
2007-07-22 21:50 ` Julian Phillips
2007-07-22 21:59 ` Johannes Schindelin
2007-07-22 22:24 ` Julian Phillips
2007-07-22 22:46 ` Jakub Narebski
2007-07-22 23:37 ` Johannes Schindelin
2007-07-22 23:02 ` Johannes Schindelin
2007-07-23 3:56 ` Shawn O. Pearce
2007-07-23 4:45 ` Junio C Hamano
2007-07-23 5:14 ` Shawn O. Pearce
2007-07-23 5:22 ` Shawn O. Pearce
2007-07-23 10:32 ` Johannes Schindelin
2007-07-23 10:42 ` Johannes Schindelin
2007-07-24 8:19 ` Marius Storm-Olsen
2007-07-24 9:02 ` Johannes Schindelin
2007-07-24 9:47 ` Junio C Hamano
2007-07-24 11:07 ` Johannes Schindelin
2007-07-24 11:14 ` Marius Storm-Olsen
2007-07-24 12:06 ` Julian Phillips
2007-07-24 12:28 ` Marius Storm-Olsen
2007-07-24 12:37 ` Johannes Schindelin
2007-07-24 13:47 ` Josef Weidendorfer
2007-07-24 13:54 ` Johannes Schindelin
2007-07-24 14:21 ` Josef Weidendorfer
2007-07-25 0:09 ` Jakub Narebski
2007-07-24 12:42 ` Johannes Schindelin
2007-07-24 13:26 ` Marius Storm-Olsen
2007-07-24 13:29 ` Marius Storm-Olsen
2007-07-24 13:33 ` Johannes Schindelin
2007-07-24 18:02 ` Marius Storm-Olsen
2007-07-24 18:30 ` Johannes Schindelin
2007-07-24 19:36 ` Marius Storm-Olsen
2007-07-24 23:15 ` Alex Riesen
2007-07-25 6:47 ` Marius Storm-Olsen
2007-07-25 9:39 ` Johannes Schindelin [this message]
2007-07-25 10:22 ` Steven Grimm
2007-07-25 11:05 ` Andy Parkins
2007-07-25 12:10 ` Marius Storm-Olsen
2007-07-25 14:09 ` Johannes Schindelin
2007-07-25 20:40 ` Linus Torvalds
2007-07-26 11:51 ` Christian MICHON
2007-07-23 8:31 ` Julian Phillips
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=Pine.LNX.4.64.0707251024390.14781@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=julian@quantumfyre.co.uk \
--cc=marius@trolltech.com \
--cc=raa.lkml@gmail.com \
--cc=spearce@spearce.org \
/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).