unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Jim Porter <jporterbugs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: montag451@laposte.net, 60083-done@debbugs.gnu.org
Subject: bug#60083: 29.0.60; eshell-elecslash when in the root directory of a remote host
Date: Wed, 21 Dec 2022 14:27:45 -0800	[thread overview]
Message-ID: <efd75ae5-0d1c-8f05-6680-331b19c63c61@gmail.com> (raw)
In-Reply-To: <838rj1apy9.fsf@gnu.org>

On 12/21/2022 4:42 AM, Eli Zaretskii wrote:
>> Date: Tue, 20 Dec 2022 22:55:24 -0800
>> Cc: 60083@debbugs.gnu.org
>> From: Jim Porter <jporterbugs@gmail.com>
>>
>> On 12/19/2022 3:29 AM, montag451 via Bug reports for GNU Emacs, the
>> Swiss army knife of text editors wrote:
>>> Thanks for looking into this. I've attached to this email a new patch
>>> which fixes the compilation warning.
>>
>> Thanks. This looks good to me now.
>>
>> Eli, should I merge this to the release branch then?
> 
> Yes, please.  But don't forget the Copyright-paperwork-exempt thingy
> in the log message.

Ok, merged to emacs-29 as 777b383dd0f61488ba4e43756cf43521f994f906.

Thanks again for the bug report/patch. Closing this bug now.






  reply	other threads:[~2022-12-21 22:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14 23:46 bug#60083: 29.0.60; eshell-elecslash when in the root directory of a remote host montag451 via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-18 10:34 ` Eli Zaretskii
2022-12-18 20:04   ` Jim Porter
2022-12-18 20:15     ` Eli Zaretskii
2022-12-19 11:29     ` montag451 via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-21  6:55       ` Jim Porter
2022-12-21 12:42         ` Eli Zaretskii
2022-12-21 22:27           ` Jim Porter [this message]
2022-12-23 19:46             ` Sean Whitton

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=efd75ae5-0d1c-8f05-6680-331b19c63c61@gmail.com \
    --to=jporterbugs@gmail.com \
    --cc=60083-done@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=montag451@laposte.net \
    /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).