From: Junio C Hamano <gitster@pobox.com>
To: "Philip Oakley" <philipoakley@iee.org>
Cc: "Git List" <git@vger.kernel.org>,
"Eric Sunshine" <sunshine@sunshineco.com>
Subject: Re: [PATCH v2b 00/16, 2 updates] Make the msvc-build scripts work again
Date: Tue, 21 Jul 2015 13:04:31 -0700 [thread overview]
Message-ID: <xmqq1tg1uvjk.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <xmqqvbdduxd5.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Tue, 21 Jul 2015 12:25:10 -0700")
Junio C Hamano <gitster@pobox.com> writes:
> "Philip Oakley" <philipoakley@iee.org> writes:
>
>> ... Ideally, if part of this
>> mainstream Git, it would get picked up automatically by them
>> (rather than being local 'fixes' endlessly carried forward).
>
> Actually, that is not "ideal", but what I want to avoid.
>
> As I do not do Windows, it simply is wrong for me to apply changes
> that are very likely to affect Windows folks without seeing their
> support first,...
Just to clarify this part. I do not do RedHat, Solaris or OSX,
either. Also MSVC may not be what GfW folks primarily target.
But the thing is that (1) Windows is so much different, and (2) GfW
folks are much more qualified to judge platform-specific issues on
Windows than I am.
Even though I may still need to have a say in the overall structure
of the changes to the upstream tree coming from them (e.g. "Don't
sprinkle #ifdef all over the generic code; instead add a wrapper or
two in compat/ to keep the generic code generic" is something I may
tell them when rejecting a change forwarded to me), I trust them a
lot more than I trust myself when it comes to what the changes do in
the platform-specific part and how they do it.
Thanks.
next prev parent reply other threads:[~2015-07-21 20:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-20 22:54 [PATCH v2b 00/16, 2 updates] Make the msvc-build scripts work again Philip Oakley
2015-07-20 22:54 ` [PATCH v2 8b/16] engine.pl: ignore invalidcontinue.obj which is known to MSVC Philip Oakley
2015-07-20 22:54 ` [PATCH v2 10b/16] engine.pl: delete the captured stderr file if empty Philip Oakley
2015-07-20 23:07 ` [PATCH v2b 00/16, 2 updates] Make the msvc-build scripts work again Junio C Hamano
2015-07-21 16:46 ` Philip Oakley
2015-07-21 19:25 ` Junio C Hamano
2015-07-21 20:04 ` Junio C Hamano [this message]
2015-07-21 20:39 ` Philip Oakley
2015-07-22 22:57 ` Ramsay Jones
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=xmqq1tg1uvjk.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=philipoakley@iee.org \
--cc=sunshine@sunshineco.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.