public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Clemens Ladisch <clemens@ladisch.de>
To: linux-kernel@vger.kernel.org
Subject: Re: What are the official opinions of the developers about develop currently code in binary, hexadecimal and assembly code?
Date: Tue, 16 Sep 2014 08:53:38 +0200	[thread overview]
Message-ID: <5417DE72.8020700@ladisch.de> (raw)
In-Reply-To: <CAK_6RwfwBVseGPZ1eWpa6We7zw9fBotiH7jhVawwXee01KU_rg@mail.gmail.com>

françai s wrote:
> The official opinions of the developers

"The developers" is not a uniform group that could hold a coherent
opinion, let alone an "official" one.

> is currently necessary develop code in binary, hexadecimal and
> assembly code?

It is usually not the preferred form for making modifications.


Regards,
Clemens

      parent reply	other threads:[~2014-09-16  6:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-15 16:57 What are the official opinions of the developers about develop currently code in binary, hexadecimal and assembly code? françai s
2014-09-15 18:05 ` françai s
2014-09-16  6:53 ` Clemens Ladisch [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=5417DE72.8020700@ladisch.de \
    --to=clemens@ladisch.de \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox