Re: Should we discuss Windows-related changes on git@vger.kernel.org?

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jul 11, 2008, 23:47 UTC
Message-ID: <alpine.DEB.1.00.0807120043150.8950@racer>
In-Reply-To: <alpine.LFD.1.10.0807111638130.3459@woody.linux-foundation.org>

Hi,

On Fri, 11 Jul 2008, Linus Torvalds wrote:

Show 18 quoted lines

> On Sat, 12 Jul 2008, Johannes Schindelin wrote:
> > 
> > I think that is a perfect example, since Hannes worked on it in 
> > mingw.git.  AFAIR a few comments came through msysGit, and were 
> > incorporated.  When everything was good for a first go at git@vger, it 
> > was sent, and the interface finalized.
> 
> Umm. Dscho - that was before the thing was merged.
> 
> Now that the basic mingw support is part of standard git, the situation 
> has changed.
> 
> That's the main issue here - if mingw support is in standard git (and it 
> is), then mingw issues that touch any non-mingw code should be discussed 
> where all the git developers are.
> 
> Can't you see the difference between the pre-merge and the post-merge 
> situation?

Sure I can.

But we are talking about 4msysgit.git, no?

At least the patches that Steffen sent were all from 4msysgit.git, and for some reason or other not necessary for Hannes' mingw.git.

We are talking about stuff like that putty thing, where people feel it would be a better idea to avoid scripts, at the cost of a higher maintenance burden.

We are talking about patches that were necessary a long time ago, but are no longer, and we should have that sorted out on the msysGit list before sending them to a list where many people could not care less for Windows, and are probably annoyed to even read as much as _this_ thread about it, let alone be bothered by patches that turn out to be stale in the first place.

_That_ is what I am arguing should be sorted out, at least the early stages, on msysGit. As we did in the past.

And that worked out rather well so far, do you disagree?

Ciao, Dscho