MLMMJ Mailing List Manager
 help / color / mirror / Atom feed
From: Ben Schmidt <mail_ben_schmidt@yahoo.com.au>
To: mlmmj@mlmmj.org
Subject: Re: [mlmmj] more than 100 lines for moderation
Date: Fri, 01 Oct 2010 09:47:31 +0000	[thread overview]
Message-ID: <4CA5AE33.1070703@yahoo.com.au> (raw)
In-Reply-To: <AANLkTimcx6HcKrOwargzPTzzYdtdNq_-6CNxHYZR1ty0@mail.gmail.com>

>> I doubt it, Florian. The changes have got into Mlmmj's version control,
>> but I don't expect they've got anywhere else yet (they haven't even made
>> it into an Mlmmj release yet).
>
> Ubuntu's package is the exact same one as we have in Debian, on which
> I'm working on.

Good to have somebody who knows.

I'm a bit of a 'grass roots' man, so I wouldn't recommend *against* a
standard ./configure && make approach, but I would too recommend Thomas'
approach. And once we have a git mirror set up (it hasn't been
forgotten!) he'll be able to give his even groovier instructions. (I'll
be using hg-git, as that is the right direction for me, of course. I
don't know whether git-remote-hg will do a lossless conversion like
hg-git does, or one compatible with hg-git's conversion, but that is
something to keep an eye on, too.)

> That's one thing I always find annoying with MLMMJ. Why are all scripts
> postfixed with ".sh"? Look into your distribution files, no scripts are
> like that. Using just "mlmmj-make-ml" (without the ".sh") directly into
> your source would be a wise change, IMHO. If you didn't know, in Debian,
> we had to do that change, because having the ".sh" extension is against
> the policy of Debian. What do you think?

There's only one, isn't there (asks the maintainer, who probably should
know...)? I agree, it is unconventional for a script designed to be run
by a user. Generally only scripts used as intermediate steps in a build,
or something like that, that are generally sourced, not executed, have
the .sh extension. I don't mind changing it, though will keep a symlink
for a while for compatibility. Likewise with mlmmj-receive. I've got to
find that patch someone made for that.

Ben.






  parent reply	other threads:[~2010-10-01  9:47 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-29 20:01 [mlmmj] more than 100 lines for moderation Florian Effenberger
2010-09-29 20:20 ` Christian Laursen
2010-09-29 22:35 ` Ben Schmidt
2010-09-30 10:27 ` Thomas Goirand
2010-09-30 14:16 ` Ben Schmidt
2010-09-30 14:31 ` Florian Effenberger
2010-09-30 23:50 ` Ben Schmidt
2010-10-01  5:14 ` Ben Schmidt
2010-10-01  8:05 ` Thomas Goirand
2010-10-01  8:44 ` Chris Webb
2010-10-01  9:47 ` Ben Schmidt [this message]
2010-10-01 23:00 ` Thomas Goirand
2010-10-02  9:31 ` Chris Webb
2010-10-02 13:24 ` Ben Schmidt
2010-10-02 18:46 ` Chris Webb

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=4CA5AE33.1070703@yahoo.com.au \
    --to=mail_ben_schmidt@yahoo.com.au \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox