Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: William Morgan <wmorgan-sup@masanjin.net>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] [patch] Add crypto_selector variable to before-edit
Date: Sat, 23 Jan 2010 07:53:04 -0500	[thread overview]
Message-ID: <1264251144-sup-4056@masanjin.net> (raw)
In-Reply-To: <1263824428-sup-6466@nemesis.home>

Hi Daniel,

I like the idea, but would prefer a dedicated "crypto-mode" hook
analogous to how we have the "reply-to" hook for setting the default
reply-to mode.
-- 
William <wmorgan-sup@masanjin.net>
_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk


  reply	other threads:[~2010-01-23 13:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-18 14:32 Daniel Schoepe
2010-01-23 12:53 ` William Morgan [this message]
2010-01-24 11:10   ` Carlos Garcia Campos
2010-01-26 15:55   ` Daniel Schoepe
2010-01-26 18:19     ` Ben Walton
2010-02-27 18:17     ` Rich Lane
2010-03-09 10:29     ` Gaute Hope
2010-03-12 22:03       ` Daniel Schoepe
2010-03-12 22:34         ` Gaute Hope

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=1264251144-sup-4056@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