procyberian/emacs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

; Fix some comment typos

Browse source
This commit is contained in:
Glenn Morris 2017-11-27 19:28:28 -05:00
parent 340f74daa8
commit 22ff46e6d8
3 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

4
lisp/gnus/message.el
View file

@ -4775,7 +4775,7 @@ to find out how to use this."
message-qmail-inject-program nil nil nil message-qmail-inject-program nil nil nil
;; qmail-inject's default behavior is to look for addresses on the ;; qmail-inject's default behavior is to look for addresses on the
;; command line; if there're none, it scans the headers. ;; command line; if there're none, it scans the headers.
;; yes, it does The Right Thing w.r.t. Resent-To and it's kin. ;; yes, it does The Right Thing w.r.t. Resent-To and its kin.
;; ;;
;; in general, ALL of qmail-inject's defaults are perfect for simply ;; in general, ALL of qmail-inject's defaults are perfect for simply
;; reading a formatted (i. e., at least a To: or Resent-To header) ;; reading a formatted (i. e., at least a To: or Resent-To header)
@ -4793,7 +4793,7 @@ to find out how to use this."
(if (functionp message-qmail-inject-args) (if (functionp message-qmail-inject-args)
(funcall message-qmail-inject-args) (funcall message-qmail-inject-args)
message-qmail-inject-args))) message-qmail-inject-args)))
;; qmail-inject doesn't say anything on it's stdout/stderr, ;; qmail-inject doesn't say anything on its stdout/stderr,
;; we have to look at the retval instead ;; we have to look at the retval instead
(0 nil) (0 nil)
(100 (error "qmail-inject reported permanent failure")) (100 (error "qmail-inject reported permanent failure"))

2
lisp/gnus/mm-decode.el
View file

@ -676,7 +676,7 @@ MIME-Version header before proceeding."
(mm-alist-to-plist (cdr ctl)) (car ctl)) (mm-alist-to-plist (cdr ctl)) (car ctl))
;; what really needs to be done here is a way to link a ;; what really needs to be done here is a way to link a
;; MIME handle back to it's parent MIME handle (in a multilevel ;; MIME handle back to its parent MIME handle (in a multilevel
;; MIME article). That would probably require changing ;; MIME article). That would probably require changing
;; the mm-handle API so we simply store the multipart buffer ;; the mm-handle API so we simply store the multipart buffer
;; name as a text property of the "multipart/whatever" string. ;; name as a text property of the "multipart/whatever" string.

2
lisp/gnus/smime.el
View file

@ -67,7 +67,7 @@
;; ;;
;; To be able to verify messages you need to build up trust with ;; To be able to verify messages you need to build up trust with
;; someone. Perhaps you trust the CA that issued your certificate, at ;; someone. Perhaps you trust the CA that issued your certificate, at
;; least I did, so I export it's certificates from my PKCS#12 ;; least I did, so I export its certificates from my PKCS#12
;; certificate with: ;; certificate with:
;; ;;
;; $ openssl pkcs12 -in mykey.p12 -cacerts -nodes > cacert.pem ;; $ openssl pkcs12 -in mykey.p12 -cacerts -nodes > cacert.pem