git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Alex Riesen <raa.lkml@gmail.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 07:51:28 -0700	[thread overview]
Message-ID: <7vhc0fv2xb.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 81b0412b0904230252k3e8197d3y8798d5b797a49c39@mail.gmail.com

Alex Riesen <raa.lkml@gmail.com> writes:

>>> 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).
>>
>> Hmm, what's the point then for me to spend time looking at them posted on
>> the list?
>
> None. But it still would be nice if you look at them when you're addressed
> directly. Please understand, maybe I'm abusing the list a little, but it looks
> like the best place to _archive_ the workarounds for this obscure platform.
> The code is of little use to general public, but in case one finds himself
> in the same situation as I am in, at least Google can help out. I think it
> happens too rare to justify your looking at them, and especially including
> them in the mainline, but hiding the code on my laptop isn't of any use
> to anyone (including me: I don't always have that laptop).

Actually, I think I probably should have phrased it more positively.

Do you think you are in a so minority situation that your "workarounds"
are valuable for nobody else?  Apparently you see value in letting them
finding your patches in the archive, so you do not expect them to be
"nobody else" but rather "a small minority".

People on minority platforms have smaller number of people in similar
situation to ask help from than people on mainstream platforms, and they
suffer from the minority status of their platforms not only with git but
about many other things.  Worse, their chance of finding solution by
digging the archive is smaller, and they would need to spend a lot more
time, than the people on other platforms.  And you know this a lot better
than I do ;-).

Even though the suffering of these people as a whole may not be much, only
because there are small number of them, as individuals they may suffer a
lot.  If we can help them without having to bend over backwards too much,
it would be a good thing.  I think we should at least try.

For example, I do not think conversion from Perl exec() to Perl system()
is worsening the code in any way in difftool.  Sure, it won't *improve*
things for general majority of people, but as long as it does not hurt
people (that includes me and others who pay maintenance cost), I do not
think we should just bury the patch in archive or in your laptop.

  parent reply	other threads:[~2009-04-23 14:53 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
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 [this message]
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=7vhc0fv2xb.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=charles@hashpling.org \
    --cc=davvid@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=markus.heidelberg@web.de \
    --cc=raa.lkml@gmail.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).