From: Nicolas Pitre <nico@fluxnic.net>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Nicholas Piggin <npiggin@gmail.com>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
Michal Marek <michal.lkml@markovi.net>
Subject: Re: [PATCH 2/2] kbuild: rename built-in.o to built-in.a
Date: Sun, 11 Feb 2018 20:26:29 -0500 (EST) [thread overview]
Message-ID: <nycvar.YSQ.7.76.1802112023470.31719@knanqh.ubzr> (raw)
In-Reply-To: <CAK7LNAQwrtJyydyvvjjtOngCkc9WLk9-0Pk57GpfCP9srAQQrg@mail.gmail.com>
On Mon, 12 Feb 2018, Masahiro Yamada wrote:
> 2018-02-11 20:15 GMT+09:00 Nicholas Piggin <npiggin@gmail.com>:
> > On Sun, 11 Feb 2018 13:38:04 +0900
> > Masahiro Yamada <yamada.masahiro@socionext.com> wrote:
> >
> >> Is my 'less' insane?
> >> Or, is this intentional behavior of 'less'?
> >
> > Interesting, my less does not do that. Instead of the raw contents
> > of the file, yours is providing output of `ar tv`, which is
> > reconstructing more of the archive metadata. I guess it is keyed
> > on the filename extension.
>
> Ah, I see. 'ar tv' and 'less' gave me the same output.
>
>
> > Do you have an alias for it, or maybe the distro patches the tool?
>
> I use Ubuntu 16.04 LTS.
>
> Not alias'ed
>
> $ type less
> less is hashed (/usr/bin/less)
> $ /usr/bin/less kernel/built-in.a | head -n 10
> rw-r--r-- 0/0 60216 Jan 1 09:00 1970 kernel/fork.o
> rw-r--r-- 0/0 3648 Jan 1 09:00 1970 kernel/exec_domain.o
> rw-r--r-- 0/0 20552 Jan 1 09:00 1970 kernel/panic.o
> rw-r--r-- 0/0 87752 Jan 1 09:00 1970 kernel/cpu.o
> rw-r--r-- 0/0 34136 Jan 1 09:00 1970 kernel/exit.o
> rw-r--r-- 0/0 41448 Jan 1 09:00 1970 kernel/softirq.o
> rw-r--r-- 0/0 40904 Jan 1 09:00 1970 kernel/resource.o
> rw-r--r-- 0/0 60968 Jan 1 09:00 1970 kernel/sysctl.o
> rw-r--r-- 0/0 4472 Jan 1 09:00 1970 kernel/sysctl_binary.o
> rw-r--r-- 0/0 12472 Jan 1 09:00 1970 kernel/capability.o
>
> Could be patched by the disto.
What do you get from:
$ echo $LESSOPEN
?
Nicolas
next prev parent reply other threads:[~2018-02-12 1:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-10 14:25 [PATCH 0/2] remove the last of incremental linking Nicholas Piggin
2018-02-10 14:25 ` [PATCH 1/2] kbuild: remove incremental linking option Nicholas Piggin
2018-02-11 6:04 ` Masahiro Yamada
2018-02-18 14:26 ` Sam Ravnborg
2018-02-18 16:53 ` Nicholas Piggin
2018-02-10 14:25 ` [PATCH 2/2] kbuild: rename built-in.o to built-in.a Nicholas Piggin
2018-02-11 4:38 ` Masahiro Yamada
2018-02-11 11:15 ` Nicholas Piggin
2018-02-12 0:57 ` Masahiro Yamada
2018-02-12 1:26 ` Nicolas Pitre [this message]
2018-02-12 3:00 ` Masahiro Yamada
2018-02-12 3:08 ` Masahiro Yamada
2018-02-18 17:10 ` Sam Ravnborg
2018-02-19 7:04 ` Nicholas Piggin
2018-02-18 23:42 ` [PATCH 0/2] remove the last of incremental linking Masahiro Yamada
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=nycvar.YSQ.7.76.1802112023470.31719@knanqh.ubzr \
--to=nico@fluxnic.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=npiggin@gmail.com \
--cc=yamada.masahiro@socionext.com \
/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.