From: Eli Zaretskii <eliz@gnu.org>
To: Jim Porter <jporterbugs@gmail.com>
Cc: 54470-done@debbugs.gnu.org
Subject: bug#54470: 29.0.50; [PATCH] Add documentation/tests for Eshell argument expansion
Date: Sun, 17 Apr 2022 10:32:42 +0300 [thread overview]
Message-ID: <834k2syxk5.fsf@gnu.org> (raw)
In-Reply-To: <55f95cab-e56f-42ef-43fb-de4fef99ea10@gmail.com> (message from Jim Porter on Sat, 16 Apr 2022 10:14:43 -0700)
> Cc: 54470@debbugs.gnu.org
> From: Jim Porter <jporterbugs@gmail.com>
> Date: Sat, 16 Apr 2022 10:14:43 -0700
>
> >> Can you try the attached patch to see if the tests pass? If it works,
> >> I'll fold it into the previous patches and resubmit them. (It works for
> >> me on an MS Windows system, but I don't have build tools on it, so I
> >> just used the binary release of 28.1 with some of the bits copied from
> >> my patches to test it out.)
> >
> > Yes, this fixes the failures, thanks.
>
> Cool, thanks. Here are final patches for merging then (only the second
> patch is changed from before, but I attached the full series for
> convenience).
Thanks, installed on the master branch, and closing the bug.
Please in the future always mention the bug number in the commit log
messages (I added that for you in this case).
next prev parent reply other threads:[~2022-04-17 7:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-20 1:34 bug#54470: 29.0.50; [PATCH] Add documentation/tests for Eshell argument expansion Jim Porter
2022-03-20 7:05 ` Eli Zaretskii
2022-03-20 20:57 ` Jim Porter
2022-03-28 2:29 ` Jim Porter
2022-03-30 4:47 ` Jim Porter
2022-03-31 7:19 ` Eli Zaretskii
2022-04-01 4:11 ` Richard Stallman
2022-04-02 5:10 ` Jim Porter
2022-04-15 12:56 ` Eli Zaretskii
2022-04-16 4:57 ` Jim Porter
2022-04-16 10:30 ` Eli Zaretskii
2022-04-16 17:14 ` Jim Porter
2022-04-17 7:32 ` Eli Zaretskii [this message]
2022-04-17 18:38 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834k2syxk5.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54470-done@debbugs.gnu.org \
--cc=jporterbugs@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 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.