all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "era eriksson" <era@iki.fi>
To: "Ilya Zakharevich" <ilya@Math.Berkeley.EDU>
Cc: 1621@emacsbugs.donarmstrong.com
Subject: bug#1621: Please move cperl micro-docs to top of the cperl-mode.el file
Date: Mon, 16 Mar 2009 22:00:31 +0200	[thread overview]
Message-ID: <1237233631.22160.1305713369@webmail.messagingengine.com> (raw)
In-Reply-To: <20090316091205.GA10436@powdermilk.math.berkeley.edu>

On Mon, 16 Mar 2009 02:12:05 -0700, "Ilya Zakharevich"
<ilya@Math.Berkeley.EDU> said:
> On Mon, Mar 16, 2009 at 10:48:40AM +0200, era eriksson wrote:
> > I'm talking about the bug's status in the Emacs Bug Tracking System at
> > http://emacsbugs.donarmstrong.com/1621 -- if Emacs maintainers don't
> > object, I'll change it to "forwarded <ilya@Math.Berkeley.EDU>" and 
> > take away the wontfix tag.  I hope it's not too far of a stretch to 
> > interpret your answer to mean that you don't really care about the 
> > Emacs BTS status of this bug report.
> > 
> > (The bug tracking system is an installation of the Debian BTS which by
> > design doesn't ever obfuscate email addresses.  I really hate this
> > "feature" because it's a regular fly paper for spam.  Maybe you would
> > prefer if I put something else than your email address in the
> > "forwarded" field, although I guess by and large the damage is already
> > done.)
> 
> Thanks, Era, I would prefer obfuscation, and not of berkeley address,
> but of ilyaz@cpan.org...

Done now, but you should be aware that the whole conversation is being
archived at the URL quoted above, in mbox format and various other
renderings.  I apologize if this was not sufficiently clear earlier. 
(It's the Cc: which does it.)

/* era */

-- 
If this were a real .signature, it would suck less.  Well, maybe not.







  reply	other threads:[~2009-03-16 20:00 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-20 18:39 bug#1621: Please move cperl micro-docs to top of the cperl-mode.el file era eriksson
2009-02-21  0:15 ` Ilya Zakharevich
2009-02-21 10:54   ` era eriksson
2009-02-21 22:53     ` Ilya Zakharevich
2009-03-16  2:10       ` era eriksson
2009-03-16  4:03         ` Ilya Zakharevich
2009-03-16  8:48           ` era eriksson
2009-03-16  9:12             ` Ilya Zakharevich
2009-03-16 20:00               ` era eriksson [this message]
2009-03-16 23:50                 ` Ilya Zakharevich
     [not found] <20070401035915.3121.73126.malonedeb@gangotri.ubuntu.com>
2008-12-18  5:14 ` Jason A. Spiro
2008-12-18 21:39   ` Stefan Monnier
2008-12-19  2:28     ` Glenn Morris
2008-12-19  6:06     ` Jason A. Spiro
2008-12-20 22:53       ` Ilya Zakharevich
2008-12-20 23:41         ` Jason A. Spiro
     [not found]           ` <20081221000241.GA17638@powdermilk.math.berkeley.edu>
2008-12-21  0:13             ` Jason A. Spiro
2020-10-15 15:11   ` Lars Ingebrigtsen

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=1237233631.22160.1305713369@webmail.messagingengine.com \
    --to=era@iki.fi \
    --cc=1621@emacsbugs.donarmstrong.com \
    --cc=ilya@Math.Berkeley.EDU \
    /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.