From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: problem with gnus-group-make-nnir-group
Date: Tue, 01 Nov 2011 09:55:22 -0400 [thread overview]
Message-ID: <878vo0rlpx.fsf@lifelogs.com> (raw)
In-Reply-To: <87r51sboo6.fsf@gnu.org>
On Tue, 01 Nov 2011 02:46:01 +0100 "Jose A. Ortega Ruiz" <jao@gnu.org> wrote:
jao> I wouldn't call it dumber, but, other than that, sounds good to me :)
The name was definitely temporary :) It's renamed to
`gnus-bound-and-true-p' now.
Ted
next prev parent reply other threads:[~2011-11-01 13:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-24 19:17 Peter Münster
2011-10-24 23:57 ` Dave Abrahams
2011-10-25 5:24 ` Peter Münster
2011-10-25 7:21 ` Dave Abrahams
2011-10-27 17:37 ` Ted Zlatanov
2011-10-30 15:59 ` Peter Münster
2011-10-30 19:00 ` Jose A. Ortega Ruiz
2011-10-31 17:19 ` Ted Zlatanov
2011-11-01 0:01 ` Jose A. Ortega Ruiz
2011-11-01 0:54 ` Ted Zlatanov
2011-11-01 1:46 ` Jose A. Ortega Ruiz
2011-11-01 13:55 ` Ted Zlatanov [this message]
2011-10-31 17:21 ` Ted Zlatanov
2011-10-31 17:38 ` Ted Zlatanov
2011-10-31 19:58 ` Peter Münster
2011-10-31 22:19 ` Ted Zlatanov
2011-10-31 23:34 ` Ted Zlatanov
2011-11-03 7:50 ` Peter Münster
2011-11-03 21:44 ` Ted Zlatanov
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=878vo0rlpx.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).