From: Jim Porter <jporterbugs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: the_wurfkreuz@proton.me, 72117@debbugs.gnu.org
Subject: bug#72117: Command doesn't execute correctly in eshell
Date: Sun, 28 Jul 2024 00:59:52 -0700 [thread overview]
Message-ID: <6483d648-d728-151f-9c9c-a74c5af2694f@gmail.com> (raw)
In-Reply-To: <a2172420-c4dd-0df7-82f0-499ed73e5706@gmail.com>
On 7/27/2024 12:14 PM, Jim Porter wrote:
> On 7/26/2024 11:40 PM, Eli Zaretskii wrote:
>> This is okay for emacs-30, thanks.
>
> Thanks. Merged to the release branch as 469bc7c9686, and closing this
> bug now.
I just realized that I forgot to add "Do not merge to master" to the
commit message (this was already fixed in a better way on master). I'm
not at my development system right now, but if no one else has merged
from the release branch to master by the time I'm back, hopefully this
message will help clarify things.
Sorry for forgetting about that.
next prev parent reply other threads:[~2024-07-28 7:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-14 19:33 bug#72117: Command doesn't execute correctly in eshell the_wurfkreuz via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-15 1:01 ` Jim Porter
2024-07-16 3:09 ` Jim Porter
[not found] ` <uDv8zx2ccT4dsHYBueowwgc6Hjuz4gs3wLRNNOXllaD4ifNUqW2-7eEYYJDjsG5VzBWGHQGoIJ1aFnbQxMLoacZR71w8v11rIb7GTfhQuus=@proton.me>
2024-07-17 2:09 ` Jim Porter
2024-07-18 5:05 ` Jim Porter
2024-07-18 9:31 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-18 15:38 ` Jim Porter
2024-07-18 16:49 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-07-18 18:26 ` Jim Porter
2024-07-27 5:18 ` Jim Porter
2024-07-27 6:40 ` Eli Zaretskii
2024-07-27 19:14 ` Jim Porter
2024-07-28 7:59 ` Jim Porter [this message]
2024-07-28 16:21 ` Jim Porter
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=6483d648-d728-151f-9c9c-a74c5af2694f@gmail.com \
--to=jporterbugs@gmail.com \
--cc=72117@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=the_wurfkreuz@proton.me \
/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).