From: Matt Armstrong <matt@lickey.com>
Cc: ding@gnus.org
Subject: Re: Hiding groups with unread messages
Date: Tue, 07 May 2002 10:07:51 -0600 [thread overview]
Message-ID: <873cx4x7oo.fsf@squeaker.lickey.com> (raw)
In-Reply-To: <vaf8z6wwe89.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Tue, 07 May 2002 10:31:50 +0200")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> After a cursory glance, your patch seems nice. I am, however, a
> little bit surprised to see a change in nnmaildir -- presumably this
> is a bug in your patch :-)
Yeah, the nnmaildir stuff was included by accident. Paul said he'd
work on a more general solution to what I was doing there (see the
archive if interested).
> Are you willing to sign copyright assignment papers for this? It's a
> pain, but necessary.
Yes, I've already done that in prep for this feature getting in.
--
Don't send mail to Gail.Browning@hole.lickey.com
The address is there for spammers to harvest.
next prev parent reply other threads:[~2002-05-07 16:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-06 19:35 Matt Armstrong
2002-05-07 8:31 ` Kai Großjohann
2002-05-07 16:07 ` Matt Armstrong [this message]
2002-05-08 17:00 ` Kai Großjohann
2002-05-08 19:36 ` Matt Armstrong
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=873cx4x7oo.fsf@squeaker.lickey.com \
--to=matt@lickey.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).