Gnus development mailing list
 help / color / mirror / Atom feed
From: Justus-bulk@Piater.name
To: Reiner Steib <Reiner.Steib@gmx.de>
Cc: ding@gnus.org
Subject: Re: nnmaildir support for nnir.el
Date: Mon, 04 Feb 2008 18:28:31 +0100	[thread overview]
Message-ID: <x8tsl08skao.fsf@tool.montefiore.ulg.ac.be> (raw)
In-Reply-To: <v91w7u3z26.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Sun, 03 Feb 2008 15:16:33 +0100")

Reiner Steib <reinersteib+gmane@imap.cc> wrote on Sun, 03 Feb 2008
15:16:33 +0100:

> Could you please provide ChangeLog entries?

(nnir-group-server): For native groups, obtain the server name from
gnus-select-method.

(nnir-run-swish++) and (nnir-run-namazu): Added support for nnmaildir.

(nnir-compose-result): New function unifying some code formerly
duplicated between nnir-run-swish++ and nnir-run-namazu.

> AFAICS, the patch is too large (< 15 lines of new code) to be
> installed without legal papers.  So we need an assignment, either for
> Gnus or for Emacs (which covers Gnus as well).  If you are willing to
> sign, I'll send you the form off-list.

This is about assigning the copyright to the FSF, right? No problem,
I'll (as)sign.

OTOH, my changes are really minimal; most of the "new" code
(nnir-compose-result) was just rearranged from elsewhere.

> When I diff this file with the version in the Gnus trunk, there are
> lots of whitespace changes.

Sorry about that. The reason is that the "download" option of
http://quimby.gnus.org/cgi-bin/cvsweb.cgi/ is broken (could somebody
fix this?). So when I just quickly wanted to try out nnir a few weeks
ago, the quickest was to simply cut & paste from the browser
window. And then I started hacking on the code without rembering to
retrieve a clean checkout first.

Anyway, I've replaced the file on my server
(http://www.montefiore.ulg.ac.be/~piater/test/nnir.el) by a clean
version.  Note that I did some superficial spambot protection by
changing @ to <at>; you may want to change them back before checking
in.

Cheers,
Justus



  reply	other threads:[~2008-02-04 17:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-03 13:04 Justus-bulk
2008-02-03 14:16 ` Reiner Steib
2008-02-04 17:28   ` Justus-bulk [this message]
     [not found]     ` <v9myq060m6.fsf_-_@marauder.physik.uni-ulm.de>
2008-03-21  7:52       ` Justus-bulk
2008-04-13 13:48     ` Reiner Steib
2008-04-13 14:58       ` Justus-bulk
2008-04-13 15:03         ` Reiner Steib
     [not found] <x8t4pcrw0pb.fsf@tool.montefiore.ulg.ac.be>
2008-02-02 20:50 ` Christoph Conrad
2008-02-02 21:21   ` Reiner Steib
2008-02-03 10:16     ` Christoph Conrad

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=x8tsl08skao.fsf@tool.montefiore.ulg.ac.be \
    --to=justus-bulk@piater.name \
    --cc=Reiner.Steib@gmx.de \
    --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).