Git development
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
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: Fri, 11 Jul 2008 16:58:28 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0807111653500.2875@woody.linux-foundation.org> (raw)
In-Reply-To: <alpine.DEB.1.00.0807120043150.8950@racer>




On Sat, 12 Jul 2008, Johannes Schindelin wrote:
> 
> But we are talking about 4msysgit.git, no?

I'm not. I'm just talking about Windows-related changes in git in 
general, that are expected to be merged into regular git one way or 
another.

If it's something that should be merged, and if it concerns code that I'm 
interested in, I want to know about it. It's that simple.

The fact that _all_ windows discussion used to be in a different area and 
not on the -git list is past. It was definitely the case that it didn't 
affect any normal git code, since it was all maintained in a separate tree 
and the normal git tree was simply not even _relevant_, and didn't even 
try to be.

But that's changed. I think the windows support merge was really quite 
well done, and was a rather clean series, and no, I don't think the unix 
people cared about it when there was so much fundamental stuff needed to 
be done - we didn't have any relevant input.

But I'd certainly _hope_ that future windows work is incremental, and at 
that point it's no longer a "drop the end result on people" situation.

		Linus

  reply	other threads:[~2008-07-11 23:59 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
2008-07-11 23:58                       ` Linus Torvalds [this message]
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.0807111653500.2875@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