unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
To: "Juanma Barranquero" <lekktu@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Move etc/future-bug into etc/JOKES ??
Date: Wed, 28 Feb 2007 15:14:58 +0100	[thread overview]
Message-ID: <m3ejoagyhp.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <f7ccd24b0702280418k31a0157bg9e9c00a6aafc718@mail.gmail.com> (Juanma Barranquero's message of "Wed\, 28 Feb 2007 13\:18\:19 +0100")

"Juanma Barranquero" <lekktu@gmail.com> writes:

> On 2/28/07, Kim F. Storm <storm@cua.dk> wrote:
>
>> They are both jokes/humor related to Emacs
>
> The point is, the content of JOKES is understandable and potentially
> funny for anyone (at least, anyone geek enough). A great deal of
> DEVEL.HUMOR is not very funny 

Actually, I find the stuff in DEVEL.HUMOR is a good deal more funny
than what's in JOKES.  And some of it has _very funny_ on its own.

>                               unless you happen to closely follow
> emacs-devel; take Handa-san's wonderful rendition of "Imagine" against
> unibyte, for example, or Stefan's joke about the "u"s in colour,
> behaviour, etc. (which he deadpaned just when I was homogenizing
> spelling all across the sources).

Why do you say those are "not very funny" unless you closely follow
emacs-devel?   I think they are fun on their own.

> Now that I think of it, I'm a bit surprised I didn't put the file
> under admin/ :)

Showing to people that it can be fun to follow emacs-devel is a good
thing. "admin" doesn't sound like a fun place to look :-)

Do we include it in the tarball?  

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2007-02-28 14:14 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1HMGG3-0006ry-7U@savannah.gnu.org>
2007-02-28 10:18 ` Move etc/future-bug into etc/JOKES ?? Kim F. Storm
2007-02-28 10:57   ` Juanma Barranquero
2007-02-28 11:27     ` David Kastrup
2007-02-28 12:22       ` Juanma Barranquero
2007-02-28 12:30         ` David Kastrup
2007-02-28 12:40           ` Juanma Barranquero
2007-02-28 11:30     ` Kim F. Storm
2007-02-28 12:18       ` Juanma Barranquero
2007-02-28 14:14         ` Kim F. Storm [this message]
2007-02-28 14:31           ` Juanma Barranquero
2007-02-28 20:02       ` Glenn Morris
2007-02-28 19:57   ` Glenn Morris
2007-02-28 20:30     ` Eli Zaretskii
2007-03-01  0:00     ` Kim F. Storm
2007-03-01  0:38       ` Juanma Barranquero
2007-03-01 10:05         ` Kim F. Storm
2007-03-01 10:28           ` David Kastrup
2007-03-01 12:37             ` Kim F. Storm
2007-03-01 15:25               ` David Kastrup
2007-03-01 16:11                 ` Kim F. Storm
2007-03-01 17:13                   ` Jay Belanger
2007-03-01 12:54       ` Kim F. Storm
2007-03-01 13:42         ` Kim F. Storm
2007-03-01 17:28           ` Drew Adams
2007-03-01 22:18             ` Kim F. Storm
2007-03-01 22:23               ` Jay Belanger
2007-03-01 22:58                 ` Drew Adams
2007-03-01 22:56               ` Drew Adams
2007-03-02  3:28             ` Richard Stallman
2007-03-02  7:46             ` Kevin Rodgers
2007-03-01  7:24     ` Karl Fogel
2007-03-01  1:09   ` Richard Stallman

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=m3ejoagyhp.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@gnu.org \
    --cc=lekktu@gmail.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 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).