From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: [PATCH 0/5] *** Resubmit: Warping via the registry ***
Date: Mon, 19 Mar 2012 13:05:17 -0400 [thread overview]
Message-ID: <87y5qw1pyq.fsf@lifelogs.com> (raw)
In-Reply-To: <1331835793-70228-1-git-send-email-dave@boostpro.com>
On Thu, 15 Mar 2012 14:23:08 -0400 Dave Abrahams <dave@boostpro.com> wrote:
DA> Note: I submitted this patch series back in October
DA> (http://permalink.gmane.org/gmane.emacs.gnus.general/80250). It still
DA> applies perfectly, but I rebased just in case. I'd really appreciate
DA> it if this series could get some attention. Further explanation of
DA> the motivation for this series is in
DA> http://article.gmane.org/gmane.emacs.gnus.general/80277. Thanks!
DA> This patch series implements the ability to warp to a message via
DA> information stored in the Gnus registry. From a user's point-of-view,
DA> this means that articles brought in from other groups by
DA> gnus-*-refer-* can be used as a jumping-off-point for further
DA> references.
Sorry for forgetting about this. I think you were still waiting on your
papers back then. I'm OK with this patch. If an XEmacs user could try
it too, that would be very helpful, but I think it's reasonable and
generally useful.
Ted
next prev parent reply other threads:[~2012-03-19 17:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 18:23 Dave Abrahams
2012-03-15 18:23 ` [PATCH 1/5] Allow gnus-summary-insert-subject to work in empty groups Dave Abrahams
2012-03-15 18:23 ` [PATCH 2/5] Record information in the registry about each article retrieved Dave Abrahams
2012-03-15 18:23 ` [PATCH 3/5] Add `gnus-select-group-with-message-id' Dave Abrahams
2012-03-15 18:23 ` [PATCH 4/5] Add `gnus-try-warping-via-registry()' Dave Abrahams
2012-03-15 18:23 ` [PATCH 5/5] Enable registry-warping as a fallback if warping via the current backend fails Dave Abrahams
2012-03-19 17:05 ` Ted Zlatanov [this message]
2012-03-22 20:59 ` [PATCH 0/5] *** Resubmit: Warping via the registry *** Lars Magne Ingebrigtsen
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=87y5qw1pyq.fsf@lifelogs.com \
--to=tzz@lifelogs.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).