From: Stefan Kangas <stefankangas@gmail.com>
To: Tim Ruffing <dev@real-or-random.org>, 72526@debbugs.gnu.org
Cc: "Björn Bidar" <bjorn.bidar@thaodan.de>
Subject: bug#72526: Needs NEWS item and doc change
Date: Tue, 7 Jan 2025 20:57:59 -0600 [thread overview]
Message-ID: <CADwFkmkg4Yx5yBdTJbwkHtCFeYAV2qX+djBXjS8FpWotDb2ZSQ@mail.gmail.com> (raw)
In-Reply-To: <51798334680bb9a85ab586eba92afb88a1446c8c.camel@real-or-random.org>
Tim Ruffing <dev@real-or-random.org> writes:
> I think the first patch (commit a7a22e7) is a good change, but it
> should get a NEWS item because it breaks existing configurations.
>
> If you had this in your netrc file:
> machine www.example.com:443 port https login foo password bar
> Then it needs to be changed to:
> machine www.example.com port https login foo password bar
>
> See https://github.com/dengste/org-caldav/issues/320 for reports of
> people running into this. This is true not only for netrc files but
> also for other authinfo backends. (For example, I've run into this
> issue with the GNOME keyring / Secret Service API.)
>
> Moreover, the docs need to be updated. doc/misc/auth.texi has an
> example that uses `yourmachine.com:80`. This should be changed to
> `yourmachine.com`. (Or better, `example.com` or some domain reserved
> for documentation, see https://www.iana.org/help/example-domains ).
Björn, could you please take a look at this?
prev parent reply other threads:[~2025-01-08 2:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r0azawml.fsf@>
2024-08-16 20:02 ` bug#72526: 31.0.50; [PATCH] Fix url-basic-auth secret search when passing username and/or port Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-16 20:02 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
2025-01-07 23:24 ` bug#72526: Needs NEWS item and doc change Tim Ruffing
2025-01-08 2:57 ` Stefan Kangas [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CADwFkmkg4Yx5yBdTJbwkHtCFeYAV2qX+djBXjS8FpWotDb2ZSQ@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=72526@debbugs.gnu.org \
--cc=bjorn.bidar@thaodan.de \
--cc=dev@real-or-random.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.