From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Backport "Fix bugs in `auth-source-netrc-parse-one'" to emacs-26
Date: Tue, 07 Aug 2018 18:09:59 +0300 [thread overview]
Message-ID: <838t5iqkl5.fsf@gnu.org> (raw)
In-Reply-To: <CAM-tV-_e-o-j_X7iVAzcy5O27cAMOYT1f25GNWVcZqC5no2wAw@mail.gmail.com> (message from Noam Postavsky on Mon, 6 Aug 2018 23:11:37 -0400)
> From: Noam Postavsky <npostavs@gmail.com>
> Date: Mon, 6 Aug 2018 23:11:37 -0400
>
> I propose to backport [1: 60ff810144] to emacs-26.
>
> Any objections?
Not from me.
next prev parent reply other threads:[~2018-08-07 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-07 3:11 Backport "Fix bugs in `auth-source-netrc-parse-one'" to emacs-26 Noam Postavsky
2018-08-07 15:09 ` Eli Zaretskii [this message]
2018-08-10 12:38 ` Noam Postavsky
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=838t5iqkl5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=npostavs@gmail.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).