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: Wed, 22 Apr 2009 22:40:01 +0200 [thread overview]
Message-ID: <81b0412b0904221340o6b2f1474oed2ad12e4f68cff3@mail.gmail.com> (raw)
In-Reply-To: <7vr5zk346d.fsf@gitster.siamese.dyndns.org>
2009/4/22 Junio C Hamano <gitster@pobox.com>:
>> Yes, FWIW. I intentionally stopped signing off patches for
>> Windows, ActiveState Perl and Cygwin: they usually harm the
>> rest of the world, while just allowing Windows users limp along.
>
> I have to wonder if you are doing that with the full understanding of what
> Signed-off-by means. I do not think the provenance of your patch is
> affected by your distaste towards the system it has effects in any way.
I'm trying to avoid being associated with development for the platform :)
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").
next prev parent reply other threads:[~2009-04-22 20:41 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 [this message]
2009-04-23 4:21 ` Junio C Hamano
2009-04-23 7:33 ` Alex Riesen
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=81b0412b0904221340o6b2f1474oed2ad12e4f68cff3@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).