unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juanma Barranquero <lekktu@gmail.com>
To: grischka <grishka@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: w32-pass-rwindow-to-system
Date: Wed, 21 Jan 2009 15:19:29 +0100	[thread overview]
Message-ID: <f7ccd24b0901210619q10018950se6f0fdeb92ff941@mail.gmail.com> (raw)
In-Reply-To: <49771D7C.7070904@gmx.de>

On Wed, Jan 21, 2009 at 14:05, grischka <grishka@gmx.de> wrote:

> That is definitely an highly optimistic point of view.

Hmm... well, OK ;-)

> I've seen
> people here fighting to protect their bugs against fixes by any
> means including obviously false arguments or even loss in common
> standards of politeness.

I don't remember obviously false arguments (in the sense of the poster
knowing that they are false), though I've seen "loss [...] of
politeness" a few times.

> Reason seems to be that bugs like any code are considered copyrighted
> work and the only way for people to gain credit in an unpaid project is
> to see their work included in history.  And of course bugs will produce
> more feedback by far than something that works flawlessly.
>
> So why should anyone be interested to throw away own work that is so
> well suited to get attention of the world as are bugs?

Sorry, I'm unable to take such a cynical view of Emacs development.
Perhaps you're right by calling me "highly optimistic".

    Juanma




  reply	other threads:[~2009-01-21 14:19 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-21 13:05 w32-pass-rwindow-to-system grischka
2009-01-21 14:19 ` Juanma Barranquero [this message]
2009-01-21 15:41   ` w32-pass-rwindow-to-system grischka
  -- strict thread matches above, loose matches on Subject: below --
2009-01-21  1:57 w32-pass-rwindow-to-system MON KEY
2009-01-21  9:29 ` w32-pass-rwindow-to-system Juanma Barranquero
2009-01-21  9:48   ` w32-pass-rwindow-to-system Lennart Borgman
2009-01-21  9:55     ` w32-pass-rwindow-to-system Juanma Barranquero
2009-01-21 10:12       ` w32-pass-rwindow-to-system Lennart Borgman
2009-01-21 10:26         ` w32-pass-rwindow-to-system Juanma Barranquero
2009-01-21 10:59           ` w32-pass-rwindow-to-system Lennart Borgman
2009-01-21 11:11             ` w32-pass-rwindow-to-system Juanma Barranquero
2009-01-21 14:09             ` w32-pass-rwindow-to-system Jason Rumney
2009-01-21 14:20               ` w32-pass-rwindow-to-system Juanma Barranquero
2009-01-21 22:12               ` w32-pass-rwindow-to-system Lennart Borgman
2009-01-21 14:23     ` w32-pass-rwindow-to-system Jason Rumney
2009-01-21 18:29       ` w32-pass-rwindow-to-system MON KEY
2009-01-21 21:58       ` w32-pass-rwindow-to-system Lennart Borgman
2009-01-21 23:03         ` w32-pass-rwindow-to-system MON KEY
2009-01-21 23:14           ` w32-pass-rwindow-to-system Lennart Borgman

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f7ccd24b0901210619q10018950se6f0fdeb92ff941@mail.gmail.com \
    --to=lekktu@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=grishka@gmx.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).