From: Robert Pluim <rpluim@gmail.com>
To: Damien Cassou <damien@cassou.me>
Cc: 38393@debbugs.gnu.org
Subject: bug#38393: 26.3.50; [PATCH][ELPA] Fix typos in dired-du.el
Date: Wed, 27 Nov 2019 09:04:22 +0100 [thread overview]
Message-ID: <m2imn5kant.fsf@gmail.com> (raw)
In-Reply-To: <87blsy73xm.fsf@cassou.me> (Damien Cassou's message of "Tue, 26 Nov 2019 21:55:49 +0100")
>>>>> On Tue, 26 Nov 2019 21:55:49 +0100, Damien Cassou <damien@cassou.me> said:
Damien> If NEW-INFO contains information for one file already in
'one' -> 'a'
And maybe 'already present' or similar.
Damien> -`dired-du-dir-info', then the new infomation replace
Damien> +`dired-du-dir-info', then the new information replace
'replaces'
Robert
next prev parent reply other threads:[~2019-11-27 8:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 20:55 bug#38393: 26.3.50; [PATCH][ELPA] Fix typos in dired-du.el Damien Cassou
2019-11-27 8:04 ` Robert Pluim [this message]
2019-11-28 6:24 ` Damien Cassou
2020-01-20 18:27 ` Stefan Kangas
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=m2imn5kant.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=38393@debbugs.gnu.org \
--cc=damien@cassou.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).