From: "Michael Kerrisk (man-pages)" <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Scot Doyle <lkml14-enLWO88E2pdl57MIdRCFDg@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] console_codes.4: Add missing escape sequence
Date: Tue, 03 Mar 2015 08:11:30 +0100 [thread overview]
Message-ID: <54F55EA2.8020103@gmail.com> (raw)
In-Reply-To: <alpine.LNX.2.11.1502271409270.274@localhost>
On 02/27/2015 03:32 PM, Scot Doyle wrote:
> On Fri, 27 Feb 2015, Michael Kerrisk (man-pages) wrote:
>> Hello Scott,
>>
>> On 02/27/2015 03:35 AM, Scot Doyle wrote:
>>> An undocumented escape sequence in drivers/tty/vt/vt.c brings the
>>> previously accessed virtual terminal to the foreground.
>>
>> Thanks. Applied. Looks like this sequence appeared with ~2.6.0 or so.
>> Do you know if this is so?
>>
>> Cheers,
>>
>> Michael
>
> "git log -p -- drivers/char/vt.c" shows that it's included in the initial
> 2005 git commit. Is there an easier way to view early kernel history than
> digging through kernel tarballs?
Tarballs is what I use in such cases... (And what I did in this case...)
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2015-03-03 7:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-27 2:35 [PATCH] console_codes.4: Add missing escape sequence Scot Doyle
2015-02-27 7:32 ` Michael Kerrisk (man-pages)
[not found] ` <54F01D8B.6090501-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-02-27 14:32 ` Scot Doyle
2015-03-03 7:11 ` Michael Kerrisk (man-pages) [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=54F55EA2.8020103@gmail.com \
--to=mtk.manpages-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=lkml14-enLWO88E2pdl57MIdRCFDg@public.gmane.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.
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.