From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: still asked later after gnus-summary-exit-no-update
Date: Wed, 08 Feb 2012 20:33:11 -0500 [thread overview]
Message-ID: <877gzwdc4o.fsf@uwo.ca> (raw)
In-Reply-To: <874nv3k3fu.fsf@gnus.org>
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Ah, right. Sorry for the confusion; this should now be fixed in No
> Gnus.
Thanks! I tested it and it works.
Dan
prev parent reply other threads:[~2012-02-09 1:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 18:32 jidanni
2011-11-29 5:42 ` Dan Christensen
2012-01-03 22:24 ` Lars Magne Ingebrigtsen
2012-01-05 14:01 ` jidanni
2012-01-06 20:47 ` Lars Magne Ingebrigtsen
2012-01-06 23:15 ` jidanni
2012-01-05 16:03 ` Dan Christensen
2012-01-06 20:46 ` Lars Magne Ingebrigtsen
2012-01-08 17:34 ` Dan Christensen
2012-01-27 17:12 ` Lars Ingebrigtsen
2012-01-28 0:57 ` Dan Christensen
2012-01-30 16:59 ` Lars Ingebrigtsen
2012-02-01 3:34 ` Dan Christensen
2012-02-01 13:18 ` Lars Ingebrigtsen
2012-02-02 23:54 ` Dan Christensen
2012-02-06 22:22 ` Lars Ingebrigtsen
2012-02-09 1:33 ` Dan Christensen [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=877gzwdc4o.fsf@uwo.ca \
--to=jdc@uwo.ca \
--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).