Re: [PATCH] Make "git reset" a builtin. (incomplete)

From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Date: Aug 23, 2007, 18:40 UTC
Message-ID: <200708232040.57014.robin.rosenberg.lists@dewire.com>
In-Reply-To: <3f4fd2640708221419w624a9920o5dc9a9fcbd680be2@mail.gmail.com>

onsdag 22 augusti 2007 skrev Reece Dunn:

> Given that you have to deal with other Windows issues (line ending,
> case insensitive file names, path format), why not put the current
> scripts in a posix porcelain directory and have a Windows porcelain
> directory where the Windows porcelain is written in C#?

Splitting effort in one language per platform would be very bad. Windows programmers would write porcelains in C# that won't run on Linux. Even when you get the programs to run, C# is a second class citizen on *nix.

> Alternatively, the porcelain could be unified to use Python and
> compiled into an executable that is installed on the Windows platform
> (removing the need to have anything other than git installed to use
> it).

We need to attract developers on Windows too and making it hard to get started with development (i.e. fix a tiny shitty bug or feature), should not require lots of setups. When we speak of dependencies in an OSS project, those that are required for development counts too.

> If not Python, then can you compile perl scripts to an executable
> form, in which case perl could be standardized on.

> This way, both camps (posix and Windows) will be happy.

Neither will be happy. Wannabe git hackers will find it hard to get started on Windows, *nix users will be unhappy because the stuff written on windows will be hard to get running on *nix etc and again windows users won't be unhappy because they don't get help with .NET issues from Linus.

-- robin