From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] [PATCH] Add new :crypto_default configuration option.
Date: Tue, 06 Oct 2009 10:16:20 -0700 [thread overview]
Message-ID: <1254849104-sup-6471@masanjin.net> (raw)
In-Reply-To: <1254417826-sup-6584@yoom.home.cworth.org>
Reformatted excerpts from Carl Worth's message of 2009-10-01:
> What makes a hook preferable over a configuration option?
I would like to support everyone's crazy desires, and a hook is worth a
thousand configuration options.
In this case, I'm sure it's only a matter of time before someone wants
to automatically determine the crypto setting based on the recipient, or
based on the message body. A hook would allow that.
> 2. Hooks are not supported forever, in which case users may find that
> things just start working when upgrading.
I am fine with this. Users be damned! (Or at least, required to read the
changelog.)
> Neither of those seem options look nice to me, and both seem easy to
> avoid with configuration options.
How so? Configuration options can change just as easily.
> If the plan is to go with (1) I'm concerned that I don't see sup
> shipping documentation for the current possible hooks. (This applies
> to configuration options too though. I think the maintainer should
> reject patches that add either without also adding documentation to
> the standard list.[*])
sup -l is supposed to produce all the hook documentation you'd need,
assuming a reasonable knowledge of Ruby.
--
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk
prev parent reply other threads:[~2009-10-06 17:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-28 22:57 Carl Worth
2009-10-01 17:07 ` William Morgan
2009-10-01 17:31 ` Carl Worth
2009-10-06 17:16 ` William Morgan [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=1254849104-sup-6471@masanjin.net \
--to=wmorgan-sup@masanjin.net \
--cc=sup-talk@rubyforge.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