From: Junio C Hamano <gitster@pobox.com>
To: markus.heidelberg@web.de
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
git@vger.kernel.org, David Aguilar <davvid@gmail.com>,
Charles Bailey <charles@hashpling.org>,
msysgit@googlegroups.com
Subject: Re: [msysGit] [PATCH] mergetool-lib: make (g)vimdiff workable under Windows
Date: Sun, 05 Apr 2009 11:41:03 -0700 [thread overview]
Message-ID: <7v63hjt03k.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 200904051232.19939.markus.heidelberg@web.de
Markus Heidelberg <markus.heidelberg@web.de> writes:
> Junio, is this something for maint? I'm not sure, since this problem
> only occurs on Windows and 'maint' isn't interesting for msysgit ATM.
I am not Dscho (nor J6t) but the last time I asked him about some other
"This makes it work better on Windows" patch, the conclusion was "only
Windows has issues and msysgit does not use 'maint'", which I agreed to be
a sensible answer for an undermanned and still-on bleeding edge project
like msysgit.
I don't mind a trivial backport for only mergetool part to the tip of
'master' (because difftool is not in master) that later makes me deal with
a small merge conflict when the refactoring topic hits master. Or Dscho
can apply such a backport and carry it as a msysgit-only patch until my
'master' is updated with the refactoring topic (at which point the
tentative patch needs to be dropped). Either would work fine with me.
prev parent reply other threads:[~2009-04-05 18:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-04 13:17 [PATCH] mergetool-lib: make (g)vimdiff workable under Windows Markus Heidelberg
2009-04-05 9:35 ` Johannes Schindelin
2009-04-05 10:32 ` Markus Heidelberg
2009-04-05 18:41 ` Junio C Hamano [this message]
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=7v63hjt03k.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=charles@hashpling.org \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=markus.heidelberg@web.de \
--cc=msysgit@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).