Git development
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Steffen Prohaska <prohaska@zib.de>,
	Johannes Sixt <johannes.sixt@telecom.at>,
	Junio C Hamano <gitster@pobox.com>,
	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: Fri, 11 Jul 2008 12:04:24 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0807111159560.2936@woody.linux-foundation.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0807111930160.8950@racer>




On Fri, 11 Jul 2008, Johannes Schindelin wrote:
> 
> Which very much includes brushing up the patches in 4msysgit, which are 
> invariably of lower quality than git.git's, because we lack a brilliant 
> maintainer like Junio.

Umm. The other side of the coin is:

 - a lot of people with good taste won't _be_ on the windows lists, 
   because there is likely a high correlation with "good taste in 
   development" and "try to avoid using windows"

 - a lot of Junio's maintenance is likely helped by the fact that (a) he 
   sees the features being discussed and the reason for them and (b) the 
   patches have in general seen comments from other people.

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

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.

		Linus

  reply	other threads:[~2008-07-11 19:05 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 [this message]
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
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.LFD.1.10.0807111159560.2936@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=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 \
    /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