all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 3736-done@debbugs.gnu.org, Sven Joachim <svenjoac@gmx.de>,
	Jason Rumney <jasonr@gnu.org>
Subject: bug#3736: 23.1.50; Please use null-device instead of /dev/null
Date: Thu, 26 Nov 2020 08:47:57 -0800	[thread overview]
Message-ID: <CADwFkmmys-UONhBzuiYz2SX0bR-A44TsVxEprPRmni0_jUpRVg@mail.gmail.com> (raw)
In-Reply-To: <871rgg87ec.fsf@gmx.de>

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

> I have applied all respective changes in the master branch which look
> obvious to me. There are still ~40 occurences of /dev/null in the lisp
> directory, but most of them are comments. So I'll close this bug.

Thanks for taking care of all that.

> If people are interested in fixing the few other places, they could do
> now by using the null-device variable or function. In case they don't
> know what's better, a new bug report for the given case would do,
> instead of keeping *this* bug report open forever.

Sounds reasonable.





  reply	other threads:[~2020-11-26 16:47 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1659.1246480655.2239.bug-gnu-emacs@gnu.org>
2009-07-02 12:22 ` bug#3736: 23.1.50; Please use null-device instead of /dev/null Michael Albinus
2009-07-02 13:03   ` Jason Rumney
2009-07-02 13:57     ` Sven Joachim
2009-07-02 14:14       ` Jason Rumney
2009-07-02 15:10         ` Michael Albinus
2020-11-19  2:31           ` Stefan Kangas
2020-11-19 16:32             ` Michael Albinus
2020-11-21 15:16               ` Michael Albinus
2020-11-26 15:28                 ` Michael Albinus
2020-11-26 16:47                   ` Stefan Kangas [this message]
2009-07-02 14:21       ` Lennart Borgman
2009-07-02 15:06     ` Michael Albinus
2009-07-02 18:49   ` Eli Zaretskii
2009-07-01 20:22 Lennart Borgman

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=CADwFkmmys-UONhBzuiYz2SX0bR-A44TsVxEprPRmni0_jUpRVg@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=3736-done@debbugs.gnu.org \
    --cc=jasonr@gnu.org \
    --cc=michael.albinus@gmx.de \
    --cc=svenjoac@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 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.