From: Jim Meyering <jim@meyering.net>
To: ding@gnus.org
Subject: [PATCH] maint: correct comment (insert "not") and hide doubled "to"
Date: Tue, 31 Jan 2012 20:42:16 +0100 [thread overview]
Message-ID: <874nvbhd5z.fsf@rho.meyering.net> (raw)
---
This is relative to the latest from gnus.git.
In case you'd like a ChangeLog entry:
2012-01-31 Jim Meyering <jim@meyering.net>
* gnus-agent.el (gnus-agent-expire-unagentized-dirs):
Correct a comment (insert "not") and hide nominally-doubled "to".
lisp/gnus-agent.el | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/lisp/gnus-agent.el b/lisp/gnus-agent.el
index d730875..5178220 100644
--- a/lisp/gnus-agent.el
+++ b/lisp/gnus-agent.el
@@ -3618,7 +3618,7 @@ articles in every agentized group? "))
(setq r d
d (directory-file-name d)))
;; if ANY ancestor was NOT in keep hash and
- ;; it's already in to-remove, add it to
+ ;; it's not already in to-remove, add it to
;; to-remove.
(if (and r
(not (member r to-remove)))
--
1.7.9.49.g25388
next reply other threads:[~2012-01-31 19:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-31 19:42 Jim Meyering [this message]
2012-01-31 23:01 ` Lars Ingebrigtsen
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=874nvbhd5z.fsf@rho.meyering.net \
--to=jim@meyering.net \
--cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).