From: Valdis.Kletnieks@vt.edu
To: Akira Hayakawa <ruby.wktk@gmail.com>
Cc: dm-devel@redhat.com, mpatocka@redhat.com, agk@redhat.com,
gregkh@linuxfoundation.org, linux-kernel@vger.kernel.org,
kernelnewbies@kernelnewbies.org
Subject: Re: [dm-devel] [RFC] dm-lc: plan to go to staging
Date: Fri, 30 Aug 2013 10:47:21 -0400 [thread overview]
Message-ID: <50810.1377874041@turing-police.cc.vt.edu> (raw)
In-Reply-To: Your message of "Fri, 30 Aug 2013 21:33:29 +0900." <52209119.3070907@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 654 bytes --]
On Fri, 30 Aug 2013 21:33:29 +0900, Akira Hayakawa said:
> Candidates:
> 1) logcache
> Not too long but explaining enough
> but looks little bit dull to me.
Descriptive but dull naming is a much underrated quality in software packages.
Consider the package HarfBuzz.
As my daughter put it, "Sounds like a bad coffee name".
rpm -qi harfbuzz says:
Description :
HarfBuzz is an implementation of the OpenType Layout engine.
(And don't get me started on the people who name packages enca, fros, serd,
yajl, or yaml. We aren't using ASR-33's anymore, brevity isn't as crucial :)
dm-logcache works just fine for me as a name for this. Or dm-lcache.
[-- Attachment #2: Type: application/pgp-signature, Size: 865 bytes --]
next prev parent reply other threads:[~2013-08-30 14:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-29 1:35 Akira Hayakawa
2013-08-29 2:05 ` Greg KH
2013-08-29 3:30 ` [dm-devel] " Alasdair G Kergon
2013-08-29 14:45 ` Mikulas Patocka
2013-08-30 12:33 ` Akira Hayakawa
2013-08-30 12:50 ` Alasdair G Kergon
2013-08-30 14:41 ` Akira Hayakawa
2013-08-30 14:47 ` Valdis.Kletnieks [this message]
2013-08-31 14:25 ` [dm-devel] [RFC] dm-writeboost: " Akira Hayakawa
2013-08-31 14:32 ` Akira Hayakawa
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=50810.1377874041@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=ruby.wktk@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®