From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Junio C Hamano <gitster@pobox.com>,
Steffen Prohaska <prohaska@zib.de>,
Johannes Sixt <johannes.sixt@telecom.at>,
msysGit <msysgit@googlegroups.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Should we discuss Windows-related changes on git@vger.kernel.org?
Date: Sat, 12 Jul 2008 00:47:37 +0100 (BST) [thread overview]
Message-ID: <alpine.DEB.1.00.0807120043150.8950@racer> (raw)
In-Reply-To: <alpine.LFD.1.10.0807111638130.3459@woody.linux-foundation.org>
Hi,
On Fri, 11 Jul 2008, Linus Torvalds wrote:
> 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
next prev parent reply other threads:[~2008-07-11 23:48 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 8:07 Should we discuss Windows-related changes on git@vger.kernel.org? Steffen Prohaska
2008-07-11 11:56 ` Johannes Schindelin
2008-07-11 15:51 ` Steffen Prohaska
2008-07-11 15:57 ` Johannes Schindelin
2008-07-11 16:24 ` Steffen Prohaska
2008-07-11 18:36 ` Johannes Schindelin
2008-07-11 19:04 ` Linus Torvalds
2008-07-11 19:40 ` Johannes Schindelin
2008-07-11 21:10 ` Steffen Prohaska
2008-07-11 21:38 ` Johannes Schindelin
2008-07-11 23:06 ` Junio C Hamano
2008-07-11 23:37 ` Johannes Schindelin
2008-07-12 8:07 ` Steffen Prohaska
2008-07-11 22:14 ` Junio C Hamano
2008-07-11 23:35 ` Johannes Schindelin
2008-07-11 23:40 ` Linus Torvalds
2008-07-11 23:47 ` Johannes Schindelin [this message]
2008-07-11 23:58 ` Linus Torvalds
2008-07-12 0:06 ` Johannes Schindelin
2008-07-12 1:07 ` Linus Torvalds
2008-07-12 7:38 ` Steffen Prohaska
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=alpine.DEB.1.00.0807120043150.8950@racer \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.sixt@telecom.at \
--cc=msysgit@googlegroups.com \
--cc=prohaska@zib.de \
--cc=torvalds@linux-foundation.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