From: Harry Putnam <reader@newsguy.com>
To: ding@gnus.org
Subject: Re: Testers wanted: New gnus backend nnselect
Date: Thu, 27 Apr 2017 12:03:29 -0400 [thread overview]
Message-ID: <86shkt7s8e.fsf@local.lan> (raw)
In-Reply-To: <87pog233uy.fsf@hanan>
Andrew Cohen <cohen@bu.edu> writes:
> TLDR: Please test the new feature found on the git repository at
> feature/gnus-select.
>
First off. TLDR?
Sorry to blunder into something that is well over my head. But I am
quite interested in searching inside gnus.
I've haven't attempted using nnir since a number of years ago and have
forgotten whatever I knew about it then.
I am a long time emacs/gnus user and have used gnus nearly exclusively
since early `Quassia' gnus. But have never really tried to learn enough
elisp etc to participate in dev.
Sorry if this next query is well known by everybody:
It is not clear (to me) how I might get this code incorporated into a
fresh version of emacs-dev (26.X) and try to figure out how to use it.
I normally (since gnus-dev was merged into main emacs-dev) just `git pull'
on my emacs branch for the newest stuff in gnus.
You mentioned its location on git repo... but I'm not sure of the
mechanics to get it.
What would I do differently to get to this work in progress the
discussion is about, feature/gnus-select?
next prev parent reply other threads:[~2017-04-27 16:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-24 3:02 Andrew Cohen
2017-04-24 20:52 ` Eric Abrahamsen
2017-04-25 0:09 ` Andrew Cohen
2017-04-25 1:01 ` Andrew Cohen
2017-04-25 15:33 ` Eric Abrahamsen
2017-04-27 16:03 ` Harry Putnam [this message]
2017-04-27 18:24 ` Eric Abrahamsen
2017-04-28 14:53 ` Harry Putnam
2017-04-28 15:23 ` Eric Abrahamsen
2017-04-28 15:44 ` Harry Putnam
[not found] ` <8eff03d9274e4d0fa58c85a87381706f@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
[not found] ` <87vapp6izc.fsf@delle7240>
2017-04-28 15:34 ` Eric Abrahamsen
2018-04-11 19:44 ` Lars 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=86shkt7s8e.fsf@local.lan \
--to=reader@newsguy.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).