Re: Should we discuss Windows-related changes on git@xxxxxxxxxxxxxxx?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On Fri, 11 Jul 2008, Linus Torvalds wrote:

>  - It may well be good to explain to the _real_ git people (eg me) what 
>    the problems in Windows land are, so that we get a first-hand view 
>    into hell, and can maybe take it into account when we make changes 
>    for other things.

Wow.  I did not think that you were a masochist.

> IOW, I think that since 1.6.0 is supposed to have native support for 
> windows, we should have patches discussed on the regular git list. The 
> ghetto that is windows can be useful for _user_ discussions, where a lot 
> of the core git people simply cannot help. But having development 
> discussions there is bad, I think.

We do have development discussions there that do not belong to git@vger.  
For example, when Hannes reimplemented the utterly broken spawn() 
implementation of Microsoft's "Run" time library.

That is not something you need to see, want to see, or can help with.

Likewise, I think it has nothing to do with the git@vger list when we add 
work-arounds until some better solution is found, and then discuss whether 
the workaround is still needed.

I cannot help to see the benefit, at least.

Once things are sorted out, I agree, it has to be sent to the git list.

Before that, however, allow us to work on another list.

Ciao,
Dscho

--
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

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux