From: Eli Zaretskii <eliz@gnu.org>
To: Wolfgang Scherer <Wolfgang.Scherer@gmx.de>
Cc: 39502@debbugs.gnu.org, dgutov@yandex.ru
Subject: bug#39502: [PATCH] Use one src status -a call for vc-src-dir-status-files
Date: Fri, 14 Feb 2020 12:05:47 +0200 [thread overview]
Message-ID: <837e0ppjpg.fsf@gnu.org> (raw)
In-Reply-To: <66c31ba7-fbb6-e287-2522-50abab0638a6@gmx.de> (message from Wolfgang Scherer on Tue, 11 Feb 2020 03:54:03 +0100)
> From: Wolfgang Scherer <Wolfgang.Scherer@gmx.de>
> Date: Tue, 11 Feb 2020 03:54:03 +0100
>
> >> I am not sure what you mean by "install the latest patch version on master"?
> >
> > You posted two versions. Maybe there will be further revisions.
> I am not planning on any :-). But I am still not sure, which master you mean. I have no write access to the repository.
Can you describe a simple use case to test your patch, and tell what
are the differences between the situation before and after the patch?
Then I will try the changes, and install them if I see no problems.
(I'm asking for details because at least part of the changes are
simply white-space changes, and it isn't easy to identify the part(s)
that really change the code workings.)
Thanks.
next prev parent reply other threads:[~2020-02-14 10:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-07 22:52 bug#39502: [PATCH] Use one src status -a call for vc-src-dir-status-files Wolfgang Scherer
[not found] ` <handler.39502.B.158111597418374.ack@debbugs.gnu.org>
2020-02-08 5:35 ` bug#39502: Acknowledgement ([PATCH] Use one src status -a call for vc-src-dir-status-files) Wolfgang Scherer
2020-02-08 9:39 ` bug#39502: [PATCH] Use one src status -a call for vc-src-dir-status-files Dmitry Gutov
2020-02-10 0:47 ` Wolfgang Scherer
2020-02-10 4:29 ` Dmitry Gutov
2020-02-11 2:54 ` Wolfgang Scherer
2020-02-11 7:46 ` Dmitry Gutov
2020-02-14 10:05 ` Eli Zaretskii [this message]
2020-02-15 2:44 ` Wolfgang Scherer
2020-08-09 11:31 ` Lars Ingebrigtsen
2020-08-09 14:13 ` Eli Zaretskii
2020-08-09 17:42 ` Dmitry Gutov
2020-08-09 19:50 ` Lars Ingebrigtsen
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=837e0ppjpg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=39502@debbugs.gnu.org \
--cc=Wolfgang.Scherer@gmx.de \
--cc=dgutov@yandex.ru \
/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).