From: Romain Francoise <romain@orebokech.com>
To: Jan Tatarik <jan.tatarik@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>, GNUS mailing list <ding@gnus.org>
Subject: Re: [gnus git] branch master updated: m0-5-112-gb0e097a =1= Allow scoring on decoded (base64, etc) bodies.
Date: Fri, 16 Nov 2012 10:10:43 +0100 [thread overview]
Message-ID: <87d2zdykto.fsf@silenus.orebokech.com> (raw)
In-Reply-To: <5n5x2rpq3gwlo8.fsf@nb-jtatarik2.xing.hh> (Jan Tatarik's message of "Wed, 14 Nov 2012 10:58:31 +0100")
Jan Tatarik <jan.tatarik@gmail.com> writes:
> Yes, that was my change breaking this. The attached patch should fix
> this.
Works for me, thanks. You have copyright papers on file, so if you provide
a fitting ChangeLog entry I can install that for you, if you like.
next prev parent reply other threads:[~2012-11-16 9:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1T9Fqc-0004AW-7n@quimby.gnus.org>
[not found] ` <87a9ul60hm.fsf@silenus.orebokech.com>
2012-11-14 9:58 ` Jan Tatarik
2012-11-16 9:10 ` Romain Francoise [this message]
2012-11-16 9:25 ` Jan Tatarik
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=87d2zdykto.fsf@silenus.orebokech.com \
--to=romain@orebokech.com \
--cc=ding@gnus.org \
--cc=jan.tatarik@gmail.com \
--cc=larsi@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).