On 22/08/07, Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: > > On Wed, 22 Aug 2007, Nicolas Pitre wrote: > > > On Wed, 22 Aug 2007, David Kastrup wrote: > > > > > If the scripting engine of choice for cobbling together prototypes > > > remains the Unix toolchain outside of git proper, then Windows users > > > will _always_ remain second class citizens since they will get to work > > > with and on new porcelain much later than the rest of the world: > > > namely when somebody bothers porting his new favorite tool for them to > > > C. > > > > Right. > > And not making the scripts builtins helps Windows users how, exactly? IIUC, the plumbing is all (or mostly) ported to C code, whereas the remaining scripts are on the porcelain side. 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#? 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). 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. - Reece - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
