all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: lekktu@gmail.com, emacs-devel@gnu.org
Subject: Re: [BUG] CVS HEAD "find-file-confirm-inexistent-file" in lisp/files.el
Date: Tue, 10 Jul 2007 12:17:11 -0400	[thread overview]
Message-ID: <E1I8IOl-00037N-A1@fencepost.gnu.org> (raw)
In-Reply-To: <86abu48k0g.fsf@blue.stonehenge.com> (merlyn@stonehenge.com)

> From: merlyn@stonehenge.com (Randal L. Schwartz)
> Date: Tue, 10 Jul 2007 06:29:19 -0700
> Cc: emacs-devel@gnu.org
> 
> >>>>> "Juanma" == Juanma Barranquero <lekktu@gmail.com> writes:
> 
> Juanma> On 7/10/07, Randal L. Schwartz <merlyn@stonehenge.com> wrote:
> >> I'm not sure what you're objecting to at this point.  Maybe nothing.
> 
> Juanma> Same that Eli was objecting: the original rudeness (made more poignant
> Juanma> by you being wrong, though you being correct wouldn't make it more
> Juanma> palatable).
> 
> To be rude, it would have to be directed at the person.  I was pointing out a
> failed process and a failed result in the most direct manner possible.  If the
> person can't distinguish themselves from their results, that's an issue for
> them, not me.

Sigh.  I have learned from hard experience that when someone tells me
they were offended by my rudeness, it's time for apologies and
rewording, not for ``it's your problem'' type of counter-attack, even
if I think I didn't say anything wrong.  Isn't it enough that two
people with quite different cultural background living half-world
apart were hurt by your wording?  Isn't it possible that what was
meant to point at ``a failed process and a failed result'' could be
reasonably read as a rude attack directed at all and every one of the
developers personally?

> And if you're contributing as a committer to a large project,
> you'd better have proper processes, *and* an ability to take heat for failure
> to comply.

We _can_ take heat, but it doesn't mean you must test us every time.

As for proper processes, show me one that will completely avoid bugs
during development, and I'm sure we will adopt it right on the spot.

> I *am* going to do what it takes for the shared result to be
> effective.

I think you would see the same efficiency if your original message
were less aggressive.

  reply	other threads:[~2007-07-10 16:17 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-01 23:05 [BUG] CVS HEAD "find-file-confirm-inexistent-file" in lisp/files.el Randal L. Schwartz
2007-07-01 23:08 ` Randal L. Schwartz
2007-07-02 19:47 ` Richard Stallman
2007-07-02 19:51   ` Randal L. Schwartz
2007-07-03  4:24     ` Richard Stallman
2007-07-02 19:59 ` Johan Bockgård
2007-07-05 19:44   ` Stefan Monnier
2007-07-06  2:31     ` Randal L. Schwartz
2007-07-06 10:03       ` Eli Zaretskii
2007-07-06 18:59       ` Richard Stallman
2007-07-09  9:01       ` Juanma Barranquero
2007-07-09 16:01         ` Randal L. Schwartz
2007-07-09 21:14           ` Juanma Barranquero
2007-07-09 23:33             ` Randal L. Schwartz
2007-07-10 11:45               ` Juanma Barranquero
2007-07-10 13:29                 ` Randal L. Schwartz
2007-07-10 16:17                   ` Eli Zaretskii [this message]
2007-07-10 18:23                     ` Stefan Monnier
2007-07-11  0:27                       ` Randal L. Schwartz
2007-07-11  3:18                       ` Stephen J. Turnbull
2007-07-11  3:45                         ` Stefan Monnier
2007-07-10 22:04                   ` Juanma Barranquero
2007-07-10 23:03                     ` Juanma Barranquero
2007-07-11  8:26                   ` tomas

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=E1I8IOl-00037N-A1@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.com \
    --cc=merlyn@stonehenge.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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.