From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: splitting docs
Date: Tue, 25 Jan 2011 14:09:02 -0800 [thread overview]
Message-ID: <87lj2863gh.fsf@gnus.org> (raw)
In-Reply-To: <871v40535h.fsf@lifelogs.com>
Ted Zlatanov <tzz@lifelogs.com> writes:
> Split tracing is done once we have the split rules. The difficulty for
> all the users seems to be the part where the nn* backend discovers that
> the split rules are data or a function and then calls them. That part
> has been stumping people for a few weeks now.
Yes... but have we looked into making the splitting less, er,
people-stumping? :-)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2011-01-25 22:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-19 14:45 Richard Riley
2010-12-19 15:34 ` Andreas Schwab
2010-12-19 16:04 ` Richard Riley
2010-12-20 17:18 ` Lars Magne Ingebrigtsen
2010-12-20 17:56 ` Richard Riley
2010-12-20 17:57 ` Lars Magne Ingebrigtsen
2011-01-19 22:17 ` Ted Zlatanov
2011-01-22 3:04 ` Lars Ingebrigtsen
2011-01-24 17:58 ` Ted Zlatanov
2011-01-24 22:08 ` Lars Ingebrigtsen
2011-01-24 22:37 ` Ted Zlatanov
2011-01-24 23:28 ` Lars Ingebrigtsen
2011-01-25 17:00 ` Ted Zlatanov
2011-01-25 22:09 ` Lars Ingebrigtsen [this message]
2011-01-26 16:59 ` Ted Zlatanov
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=87lj2863gh.fsf@gnus.org \
--to=larsi@gnus.org \
--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).