From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Daniel Semyonov <daniel@dsemy.com>
Cc: 64202@debbugs.gnu.org
Subject: bug#64202: [PATCH] Gnus: Add back end for Atom feeds (nnatom)
Date: Wed, 19 Jul 2023 08:39:08 -0700 [thread overview]
Message-ID: <87wmyvhpwj.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87zg3s8qjl.fsf@dsemy.com> (Daniel Semyonov's message of "Wed, 19 Jul 2023 07:37:50 +0300")
On 07/19/23 07:37 AM, Daniel Semyonov wrote:
>>>>>> Eric Abrahamsen writes:
>
> >> In any case, I still didn't have much time to work on the backend
> >> unfortunately, but I attached a patch which incorporates the
> >> fixes from my last message + changes based on comments from
> >> Stefan.
> >>
> >> Things left to do: 1. Ensure support for none-libxml builds (I
> >> should probably figure out how ERT works to make this a non-issue
> >> going forward). 2. Factor out nnfeed.el and base nnatom on top
> >> of it (shouldn't be hard). 3. Add support for RSS (and steal
> >> cool stuff from nnrss). 4. Support Atom feeds linked in HTML
> >> documents.
>
> > Is there a repository somewhere where you're working on this?
>
> I have <git.sr.ht/~dsemy/nnatom>, but I haven't updated it since posting
> the first version of the patch, when I started developing it "inside"
> the Emacs repo (not sure of the correct terminology).
> Honestly, I'm not the best with Git, so I'm not really sure what would
> be the best way to do this. Should I just create a mirror (or whatever
> its called) of the Emacs repo with my patch applied and work on it from
> there?
It's not a big deal, I just thought if you had an ongoing branch
someplace publicly available I would pull it and follow along. It's a
little harder to see what's changed each time you send a patch as an
attachment, but it's not that important.
next prev parent reply other threads:[~2023-07-19 15:39 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-21 7:08 bug#64202: [PATCH] Gnus: Add back end for Atom feeds (nnatom) Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-21 9:50 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-21 13:02 ` Eli Zaretskii
2023-06-21 14:26 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-25 10:07 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-26 13:26 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-26 14:52 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-01 8:39 ` Eli Zaretskii
2023-07-01 11:33 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-02 22:59 ` Eric Abrahamsen
2023-07-03 0:00 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-03 4:01 ` Eric Abrahamsen
2023-07-05 12:36 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-05 17:17 ` Eric Abrahamsen
2023-07-05 18:50 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-05 19:07 ` Eric Abrahamsen
2023-07-15 0:59 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-15 1:26 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-18 17:32 ` Eric Abrahamsen
2023-07-19 4:37 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-19 15:39 ` Eric Abrahamsen [this message]
2023-12-08 3:31 ` Husain Alshehhi
2023-12-08 3:31 ` Husain Alshehhi
[not found] ` <875y1974k0.fsf@>
2023-12-08 9:32 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-08 16:01 ` Eric Abrahamsen
2023-12-08 16:26 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-09 11:03 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-09 13:59 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-12 18:08 ` Eric Abrahamsen
2023-12-16 15:14 ` Thomas Fitzsimmons
2023-12-17 0:13 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-17 12:10 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-12-17 15:55 ` Thomas Fitzsimmons
2023-12-17 16:15 ` Eric Abrahamsen
2023-12-17 20:27 ` Eric Abrahamsen
2024-02-02 1:35 ` James Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-04 12:38 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-07 17:49 ` bug#64202: bug#66188: 29.1; Include Atom feed reader Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-08 4:27 ` James Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-08 11:42 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-09 3:54 ` James Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-09 14:01 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-09 20:06 ` James Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-09 22:34 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-10 0:15 ` James Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-22 2:17 ` James Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-22 17:10 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-23 16:27 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-24 14:49 ` James Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-02-27 5:02 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-03 2:40 ` James Thomas via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-18 16:58 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-24 13:35 ` bug#64202: " Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-06 9:01 ` bug#66188: " Eli Zaretskii
2024-04-18 9:01 ` Eli Zaretskii
2024-04-21 0:46 ` Eric Abrahamsen
2024-04-21 18:41 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-22 3:11 ` Eric Abrahamsen
2024-04-22 22:44 ` bug#64202: " Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-23 14:34 ` Eric Abrahamsen
2024-04-23 22:07 ` Daniel Semyonov via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-24 14:19 ` Eric Abrahamsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wmyvhpwj.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=64202@debbugs.gnu.org \
--cc=daniel@dsemy.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).