From: Jambunathan K <kjambunathan@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
Bozhidar Batsov <bozhidar@batsov.com>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: helpers.el [was: ... lisp/emacs-lisp/helpers.el...]
Date: Sat, 30 Nov 2013 13:37:02 +0530 [thread overview]
Message-ID: <87zjoms47t.fsf@gmail.com> (raw)
In-Reply-To: <946783d5-d410-4ee8-87c8-20a2e80258e5@default> (Drew Adams's message of "Fri, 29 Nov 2013 15:50:30 -0800 (PST)")
Drew Adams <drew.adams@oracle.com> writes:
> `helpers.el' is an *un*helpful file name.
I thought of GNU ELPA (also as) a waiting-room or a staging area.
----------------------------------------------------------------
Folks,
What we need is a meaning-less name - in corporate-speak a code-name, a
release name. We shouldn't allow questions like "What goes here and
what doesn't go here?" to arise.
Get creative.
Dig in to mythology, folklore, sci-fi or resort to just plain absuridty.
Call it
- absurd
- bazaar (flea market)
- confused
- hairball
- hammock
- inbox
- memo
- mystic
- noodle
- pandora
- piggy (bank)
- rug
- sack
- sandbox
- spaghetti
- just base64 encode your favorite star's name
----------------------------------------------------------------
next prev parent reply other threads:[~2013-11-30 8:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1VmRIu-00084e-Mh@vcs.savannah.gnu.org>
2013-11-29 18:23 ` [Emacs-diffs] trunk r115287: * lisp/emacs-lisp/helpers.el (string-empty-p): New function Stefan Monnier
2013-11-29 21:29 ` Bozhidar Batsov
2013-11-29 23:50 ` helpers.el [was: ... lisp/emacs-lisp/helpers.el...] Drew Adams
2013-11-30 7:41 ` Bozhidar Batsov
2013-11-30 8:07 ` Jambunathan K [this message]
2013-12-04 15:55 ` Ted Zlatanov
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=87zjoms47t.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=bozhidar@batsov.com \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.