unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: master 1914d94 2/2: Change how Dired displays available space
Date: Thu, 02 Dec 2021 17:47:55 +0100	[thread overview]
Message-ID: <87tufrymv8.fsf@gnus.org> (raw)
In-Reply-To: <87sfvbm1j3.fsf@gmx.de> (Michael Albinus's message of "Thu, 02 Dec 2021 17:09:36 +0100")

Michael Albinus <michael.albinus@gmx.de> writes:

>> My assumption was that (as for the first bit) that not translating the
>> "total x" thing wouldn't be catastrophic, so that could be adjusted
>> afterwards.
>
> "Afterwards" is in dired-insert-directory? As said, this is not always
> in play.

No, as in "after this commit was pushed".  😀

> I do not oppose heavily to this change. The advantage is, that the
> boring "adjust the free disk space" must not be implemented again and
> again in all insert-directory incarnations. But a coordinated change
> would have been better ...

My hope that this change wouldn't actually break anything for anybody,
so whatever glitches appear could be fixed as discovered, so no
coordination would be necessary.

> Well, what about this change in etc/NEWS:

Sure, looks good to me.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no



  reply	other threads:[~2021-12-02 16:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20211201222724.19544.19533@vcs0.savannah.gnu.org>
     [not found] ` <20211201222726.7AFF521362@vcs0.savannah.gnu.org>
2021-12-02 14:55   ` master 1914d94 2/2: Change how Dired displays available space Michael Albinus
2021-12-02 15:41     ` Lars Ingebrigtsen
2021-12-02 16:09       ` Michael Albinus
2021-12-02 16:47         ` Lars Ingebrigtsen [this message]
2021-12-02 17:21           ` [External] : " Drew Adams
2021-12-02 18:46           ` Michael Albinus

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=87tufrymv8.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=michael.albinus@gmx.de \
    /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).