From: Jon Dugan <jdugan@es.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] [PATCH] minor nits in exception apology message
Date: Wed, 28 Oct 2009 15:22:32 -0500 [thread overview]
Message-ID: <1256760970-sup-8118@arrakis.es.net> (raw)
In-Reply-To: <1256760295-sup-9873@peray>
Excerpts from Nicolas Pouillard's message of Wed Oct 28 15:05:27 -0500 2009:
> Excerpts from Jon Dugan's message of Wed Oct 28 18:14:51 +0100 2009:
> > make path to the exception log relative to BASE_DIR
> > fix a typo in email address of list.
> >
> > ---
> > bin/sup | 4 ++--
> > 1 files changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/bin/sup b/bin/sup
> > index 7641401..a881284 100755
> > --- a/bin/sup
> > +++ b/bin/sup
> > @@ -360,8 +360,8 @@ unless Redwood::exceptions.empty?
> > ----------------------------------------------------------------
> > I'm very sorry. It seems that an error occurred in Sup. Please
> > accept my sincere apologies. If you don't mind, please send the
> > -contents of ~/.sup/exception-log.txt and a brief report of the
> > -circumstances to sup-talk at rubyforge dot orgs so that I might
> > +contents of #{BASE_DIR}/.sup/exception-log.txt and a brief report of the
> > +circumstances to sup-talk at rubyforge dot org so that I might
>
> I think the *orgs* was on purpose.
I was wondering about that. It seemed odd to me to be obfuscating the email
address at all in this context since this is an error message not a webpage.
In my mind the usability enhancement of being able to cut and paste the email
address would increase the likelyhood of people reporting errors.
Obviously not a big deal either way...
Jon
--
Jon M. Dugan <jdugan@es.net>
ESnet Network Engineering Group
Lawrence Berkeley National Laboratory
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
next prev parent reply other threads:[~2009-10-28 20:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-28 17:14 Jon Dugan
2009-10-28 20:05 ` Nicolas Pouillard
2009-10-28 20:22 ` Jon Dugan [this message]
2009-10-29 10:29 ` Nicolas Pouillard
2009-10-30 21:53 ` William Morgan
2009-10-31 11:28 ` Tero Tilus
2009-11-01 14:39 ` William Morgan
2009-11-01 15:24 ` Nicolas Pouillard
2009-11-01 16:19 ` William Morgan
2009-11-01 16:48 ` Nicolas Pouillard
2009-11-01 17:30 ` William Morgan
2009-11-01 17:49 ` Nicolas Pouillard
2009-11-01 20:30 ` rick.tessner
2009-11-02 7:19 ` Tero Tilus
2009-11-02 15:07 ` William Morgan
2009-11-02 7:25 ` [sup-talk] Sup Issues Task Force (SITF) Tero Tilus
2009-11-02 9:14 ` Israel Herraiz
2009-11-02 15:08 ` William Morgan
2009-11-03 1:45 ` Tero Tilus
[not found] ` <1256940689-sup-888@arrakis.es.net>
2009-11-01 14:45 ` [sup-talk] [PATCH] minor nits in exception apology message William Morgan
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=1256760970-sup-8118@arrakis.es.net \
--to=jdugan@es.net \
--cc=sup-talk@rubyforge.org \
/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