From: Mads Martin Joergensen <mmj@mmj.dk>
To: mlmmj@mlmmj.org
Subject: Re: mlmmj-1.2.16-PRE2 released
Date: Mon, 03 Nov 2008 20:24:24 +0000 [thread overview]
Message-ID: <20081103202424.GR28005@mmj.dk> (raw)
In-Reply-To: <1225668062.14901.42.camel@mopo-laptop>
* Chris Webb <chris@arachsys.com> [Nov 03. 2008 19:20]:
> "Morten K. Poulsen" <mopo@fabletech.com> writes:
>
> > Am I still missing something?
>
> For a long time now, I've done something clumsy along the lines of
>
> find . -name '*recieve*' | while read F; do mv $F `sed 's/recieve/receive/g' <<< "$F"`; done
> find . -name '*voodo*' | while read F; do mv $F `sed 's/voodo/voodoo/g' <<< "$F"`; done
> find . -type f | while read F; do sed -e s/recieve/receive/g -e s/voodo/voodoo/g -i $F; done
>
> as part of my package build for mlmmj. It'd be nice to get these trivial
> spelling clean-ups upstream: how would you feel about a patch correcting the
> spelling of 'receive' and 'voodoo' through the code and filenames if I were
> to generate one?
>
> Of course, we could install a symlink from mlmmj-receive-strip to
> mlmmj-recieve-strip so nothing will break for people using the old,
> incorrectly spelled binary name.
If someone makes the autotools cope with installing a symlink, I'll make
a patch that warns in the logs something along the line of:
"You are using the old obsolete name for invoking mlmmj-recieve. Please
correct your invocation to use mlmmj-receive."
do-all-the-voodo-here is not a binary, so I couldn't care less about
that one.
--
Mads Martin Joergensen, http://mmj.dk
"Why make things difficult, when it is possible to make them cryptic
and totally illogical, with just a little bit more effort?"
-- A. P. J.
prev parent reply other threads:[~2008-11-03 20:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-02 23:21 mlmmj-1.2.16-PRE2 released Morten K. Poulsen
2008-11-03 18:20 ` Chris Webb
2008-11-03 18:33 ` Chris Webb
2008-11-03 20:24 ` Mads Martin Joergensen [this message]
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=20081103202424.GR28005@mmj.dk \
--to=mmj@mmj.dk \
--cc=mlmmj@mlmmj.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 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.