From: chiachen <luojiazhen@gmail.com>
To: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
Cc: wuzhouhui <wuzhouhui14@mails.ucas.ac.cn>,
Aruna Hewapathirane <aruna.hewapathirane@gmail.com>,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: how to determine whether the source code is same between two kernels
Date: Sun, 12 May 2019 07:47:49 +0800 [thread overview]
Message-ID: <CAH_+V=coirv3iKO+CExoLuR1LJb_7zxoqZDFs5k5mXep7gcYfA@mail.gmail.com> (raw)
In-Reply-To: <20068.1557582805@turing-police>
[-- Attachment #1.1: Type: text/plain, Size: 649 bytes --]
You could use "Beyond Compare" to compare these two bin or source files.
Valdis Klētnieks <valdis.kletnieks@vt.edu> 于2019年5月11日周六 下午9:53写道:
> On Sat, 11 May 2019 09:20:22 -0400, Aruna Hewapathirane said:
>
> > Seriously ? Since when are you working for turing-police ?
>
> I'm semi-retired. :)
>
> And there's two other systems in the room called wintermute and
> neuromancer.
> Hopefully you can figure it out from there. :)
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
[-- Attachment #1.2: Type: text/html, Size: 1174 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
prev parent reply other threads:[~2019-05-11 23:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 8:52 how to determine whether the source code is same between two kernels wuzhouhui
2019-05-08 9:25 ` Greg KH
2019-05-08 9:43 ` wuzhouhui
2019-05-08 10:08 ` greg kh
2019-05-08 13:43 ` Valdis Klētnieks
2019-05-11 2:11 ` Aruna Hewapathirane
2019-05-11 3:58 ` Valdis Klētnieks
2019-05-11 13:20 ` Aruna Hewapathirane
2019-05-11 13:53 ` Valdis Klētnieks
2019-05-11 23:47 ` chiachen [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='CAH_+V=coirv3iKO+CExoLuR1LJb_7zxoqZDFs5k5mXep7gcYfA@mail.gmail.com' \
--to=luojiazhen@gmail.com \
--cc=aruna.hewapathirane@gmail.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=valdis.kletnieks@vt.edu \
--cc=wuzhouhui14@mails.ucas.ac.cn \
/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 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 NNTP newsgroup(s).