unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Eshel Yaron <me@eshelyaron.com>
Cc: 64126-done@debbugs.gnu.org
Subject: bug#64126: [PATCH] New command 'eww-copy-alternate-url'
Date: Sat, 24 Jun 2023 15:00:51 +0300	[thread overview]
Message-ID: <83mt0pysr0.fsf@gnu.org> (raw)
In-Reply-To: <m14jn0pw9w.fsf@eshelyaron.com> (message from Eshel Yaron on Wed,  21 Jun 2023 20:20:27 +0300)

> From: Eshel Yaron <me@eshelyaron.com>
> Cc: 64126@debbugs.gnu.org
> Date: Wed, 21 Jun 2023 20:20:27 +0300
> 
> >> Yes, websites very often use these alternate links to point to their
> >> RSS/Atom feeds.  Should I add a couple of words about that in the NEWS
> >> entry as well?
> >
> > Yes, a few more words of explanation would be good there.
> 
> Sure, I've added a few words about alternate links to the NEWS entry in
> the following (updated) patch:

Thanks, installed (with a couple of minor fixes) on the master branch,
and closing the bug.





      reply	other threads:[~2023-06-24 12:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-17 11:07 bug#64126: [PATCH] New command 'eww-copy-alternate-url' Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-17 13:07 ` Eli Zaretskii
2023-06-17 14:08   ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-17 17:08     ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-21  6:01       ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-21 11:00         ` Eli Zaretskii
2023-06-21 12:02           ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-21 14:04     ` Eli Zaretskii
2023-06-21 17:20       ` Eshel Yaron via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-24 12:00         ` Eli Zaretskii [this message]

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=83mt0pysr0.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=64126-done@debbugs.gnu.org \
    --cc=me@eshelyaron.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).