public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Bill Lear <rael@zopyra•com>
To: Markus Elfring <Markus.Elfring@web•de>
Cc: Jeff King <peff@peff•net>, git@vger•kernel.org
Subject: Re: Fix signal handler
Date: Wed, 3 Feb 2010 10:26:32 -0600	[thread overview]
Message-ID: <19305.41912.44282.604758@blake.zopyra.com> (raw)
In-Reply-To: <4B699E7C.1030007@web.de>

On Wednesday, February 3, 2010 at 17:04:12 (+0100) Markus Elfring writes:
>> If your patch is not too intrusive, and especially if you can demonstrate
>> that it is a problem on a real-world system, then I think your patch would
>> be considered for inclusion upstream.
>>   
>I have got the feeling that my corresponding update suggestion (in
>source code form) would become intrusive to some degree. If I do not get
>an indication that issues from word-tearing in signal handlers is a
>mentionable problem here, I assume that your acceptance is low for
>potential fixes from every software developer (including me).

Do the words "insufferable !@#$!%%$" mean anything to you?  I mean,
seriously, you are WELCOME TO SUBMIT A PATCH FOR THIS.  Do it!  Go
ahead, write it!  We would love to see it.  Fix things, make things
better!  Don't continue to whine and waste people's time.  ALL PATCHES
ARE INTRUSIVE.  JUST SUBMIT A PATCH!


Bill

  reply	other threads:[~2010-02-03 16:26 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-02 16:14 Fix signal handler Markus Elfring
2010-02-02 20:58 ` Jeff King
2010-02-02 21:44   ` Markus Elfring
2010-02-02 22:32     ` Jeff King
2010-02-03 10:20       ` Markus Elfring
2010-02-03 10:29         ` Jeff King
2010-02-03 11:55           ` Markus Elfring
2010-02-03 13:12             ` Thomas Rast
2010-02-03 15:46               ` Markus Elfring
2010-02-03 15:52                 ` Shawn O. Pearce
2010-02-03 15:53                 ` Andreas Ericsson
2010-02-03 16:24                   ` Markus Elfring
2010-02-04  7:23                     ` Andreas Ericsson
2010-02-03 15:17             ` Jeff King
2010-02-03 16:04               ` Markus Elfring
2010-02-03 16:26                 ` Bill Lear [this message]
2010-02-09 18:01   ` Markus Elfring
2010-02-09 23:49     ` Daniel Barkalow
2010-02-10 17:08     ` [PATCH] " Markus Elfring
2010-02-10 17:14       ` Shawn O. Pearce
2010-02-10 17:35         ` Jeff King
2010-02-10 17:33       ` Jeff King
2010-02-13 13:30         ` Markus Elfring
2010-02-14  6:47           ` Jeff King
2010-02-14 10:19             ` Junio C Hamano
2010-02-18 16:31               ` Markus Elfring
2010-02-18 20:06                 ` Junio C Hamano
2010-02-19 11:05                   ` Markus Elfring
2010-02-22 12:10                   ` [PATCH] Fix a " Markus Elfring
2010-02-22 18:31                     ` Junio C Hamano
2010-02-23  8:55                       ` Markus Elfring
2010-02-23  9:10                         ` Markus Elfring
2010-02-23 21:48                         ` Junio C Hamano
2010-02-24 10:38                           ` Markus Elfring
2010-02-24 10:51                             ` Andreas Ericsson
2010-02-24 11:08                           ` Markus Elfring

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=19305.41912.44282.604758@blake.zopyra.com \
    --to=rael@zopyra$(echo .)com \
    --cc=Markus.Elfring@web$(echo .)de \
    --cc=git@vger$(echo .)kernel.org \
    --cc=peff@peff$(echo .)net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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