From: Alex Riesen <raa.lkml@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: David Aguilar <davvid@gmail.com>,
git@vger.kernel.org, charles@hashpling.org,
markus.heidelberg@web.de
Subject: Re: [PATCH] Wait for git diff to finish in git difftool
Date: Thu, 23 Apr 2009 09:33:48 +0200 [thread overview]
Message-ID: <81b0412b0904230033n35f1117fmea4432a2f2140d25@mail.gmail.com> (raw)
In-Reply-To: <7v4owgyp8x.fsf@gitster.siamese.dyndns.org>
2009/4/23 Junio C Hamano <gitster@pobox.com>:
> Alex Riesen <raa.lkml@gmail.com> writes:
>> Frankly, I just always forget about it. The patches to my windows
>> repository are mostly just hacks to either make it pass test suite or
>> workaround another, the platforms specific, stupidity. Not sure anyone
>> is actually interested in them (because, I repeat, they mostly hurt
>> everyone else, while making the platforms port "a little working").
>
> What do you really mean? These patches add maintenance burden but its
> benefit nobody would care about, and should not be applied?
Maintenance _and_ run-time. It is your decision, but yes, I kind of hate
the idea of them being applied.
In plain words: please don't apply MY patches with words "Windows"
or "Cygwin" in message body, unless I beg you to (and even then,
consider me heavily drugged).
next prev parent reply other threads:[~2009-04-23 7:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 7:27 [PATCH] Wait for git diff to finish in git difftool Alex Riesen
2009-04-22 8:26 ` David Aguilar
2009-04-22 11:04 ` Alex Riesen
2009-04-22 18:59 ` Junio C Hamano
2009-04-22 20:40 ` Alex Riesen
2009-04-23 4:21 ` Junio C Hamano
2009-04-23 7:33 ` Alex Riesen [this message]
2009-04-23 8:26 ` Junio C Hamano
2009-04-23 9:52 ` Alex Riesen
2009-04-23 14:00 ` Sverre Rabbelier
2009-04-23 14:51 ` Junio C Hamano
2009-04-23 18:57 ` Alex Riesen
2009-04-23 19:08 ` Alex Riesen
2009-04-23 19:18 ` [PATCH] Explain seemingly pointless use of system in difftool Alex Riesen
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=81b0412b0904230033n35f1117fmea4432a2f2140d25@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=charles@hashpling.org \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=markus.heidelberg@web.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;
as well as URLs for NNTP newsgroup(s).