From: "Ludovic Courtès" <ludo@gnu.org>
To: Mark H Weaver <mhw@netris.org>
Cc: 44347-done@debbugs.gnu.org, Jesse Gibbons <jgibbons2357@gmail.com>
Subject: bug#44347: mingetty --no-clear is hard-coded
Date: Thu, 03 Dec 2020 18:12:14 +0100 [thread overview]
Message-ID: <87lfeebyq9.fsf@gnu.org> (raw)
In-Reply-To: <87o8kgpw0d.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 01 Nov 2020 23:12:02 +0100")
This was fixed by commit e3ae31347882b25e1513e4475616fb6e4497e280.
Closing!
prev parent reply other threads:[~2020-12-03 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 15:16 bug#44347: mingetty --no-clear is hard-coded Jesse Gibbons
2020-11-01 16:30 ` Mark H Weaver
2020-11-01 16:37 ` Mark H Weaver
2020-11-01 22:12 ` Ludovic Courtès
2020-12-03 17:12 ` Ludovic Courtès [this message]
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=87lfeebyq9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=44347-done@debbugs.gnu.org \
--cc=jgibbons2357@gmail.com \
--cc=mhw@netris.org \
/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/guix.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.