From: reader@newsguy.com
To: ding@gnus.org
Subject: Re: `gnus-uu-digest-post-forward' grabs too much
Date: Wed, 18 Apr 2007 05:09:22 -0400 [thread overview]
Message-ID: <877isa59rx.fsf@newsguy.com> (raw)
In-Reply-To: <b4m7isbttix.fsf@jpl.org>
Katsumi Yamaoka <yamaoka@jpl.org> writes:
>>>>>> In <87mz18y5fn.fsf@newsguy.com> reader@newsguy.com wrote:
>
>> I'm noticing what may be a small bug in `gnus-uu-digest-post-forward'
>> (S-O-p).
>
>> If I mark a series with # and then use `S-O-p' all is well, but if I
>> then mark a new series with # while in the same NG, and use `S-O-p' I
>> get both the new and the old series.
>
> That's my fault, is only in No Gnus. I've fixed this bug in the
> Gnus CVS trunk right now. Could you try it?
Thanks for speedy reply. Yes it seems to work as expected now
prev parent reply other threads:[~2007-04-18 9:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-16 10:33 reader
2007-04-17 6:16 ` Katsumi Yamaoka
2007-04-18 9:09 ` reader [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=877isa59rx.fsf@newsguy.com \
--to=reader@newsguy.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).