Archive of RubyForge sup-devel mailing list
 help / color / mirror / Atom feed
From: Ben Walton <bwalton@artsci.utoronto.ca>
To: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] [PATCH] Stop worrying notice when encrypted email not signed
Date: Sun, 17 Oct 2010 21:55:27 -0400	[thread overview]
Message-ID: <1287366885-sup-9753@pinkfloyd.chass.utoronto.ca> (raw)
In-Reply-To: <AANLkTinEiJYb+-gPcEUkw=1ARwf9mENbF7EOi1eiLfWr@mail.gmail.com>

Excerpts from Hamish D's message of Sun Oct 17 18:41:45 -0400 2010:

> assumed to not be signed at all. This fix also saves the
> encrypted messages to a temp file with a suffix of .asc
> to stop gpg complaining about "unknown suffix".

How about submitting these as separate patches?  They are actually to
different issues.

They look good though.

Thanks
-Ben
--
Ben Walton
Systems Programmer - CHASS
University of Toronto
C:416.407.5610 | W:416.978.4302

_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel


      reply	other threads:[~2010-10-18  2:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-17 22:41 Hamish D
2010-10-18  1:55 ` Ben Walton [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=1287366885-sup-9753@pinkfloyd.chass.utoronto.ca \
    --to=bwalton@artsci.utoronto.ca \
    --cc=sup-devel@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