public inbox for elfutils@sourceware.org
 help / color / mirror / Atom feed
From: Matheus Tavares Bernardino <quic_mathbern@quicinc.com>
To: <mark@klomp.org>
Cc: <bcain@quicinc.com>, <elfutils-devel@sourceware.org>,
	<quic_apinski@quicinc.com>, <quic_mathbern@quicinc.com>,
	<sidneym@quicinc.com>
Subject: Re: [PATCH v3] Hexagon: implement machine flag check
Date: Thu, 4 Apr 2024 16:56:34 -0300	[thread overview]
Message-ID: <7b3f842570fd15bbe302093399695613a1b425a6.1712259987.git.quic_mathbern@quicinc.com> (raw)
In-Reply-To: <20240404194311.GI19937@gnu.wildebeest.org>

On Thu, Apr 04, 2024 at 21:43:11 +0200, Mark Wielaard wrote:
>
> 
> Note that we also have a public-inbox instance, which is useful in
> some cases since you can address patches by message-id:
> https://inbox.sourceware.org/elfutils-devel/d198f1806a486bd5129c996f10680b947ecdc581.1712087613.git.quic_mathbern@quicinc.com/

Awesome! I much rather prefer the public-inbox interface :) Thanks!

BTW, just out of curiosity, since the last incident with xz's backdoor
(which apparently involved malicious code disguised as a test binary),
has the elfutils community already considered using something like
Dockerfiles to generate the tests/*.ko.bz2 binaries instead of checking
than in the git repo? Just something that crossed my mind while I was
developing these patches.

  reply	other threads:[~2024-04-04 19:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-04 17:19 Matheus Tavares Bernardino
2024-04-04 19:43 ` Mark Wielaard
2024-04-04 19:56   ` Matheus Tavares Bernardino [this message]
2024-04-04 20:01     ` Andrew Pinski
2024-04-05 14:45     ` Mark Wielaard
2024-04-05 17:26       ` Matheus Tavares Bernardino

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=7b3f842570fd15bbe302093399695613a1b425a6.1712259987.git.quic_mathbern@quicinc.com \
    --to=quic_mathbern@quicinc.com \
    --cc=bcain@quicinc.com \
    --cc=elfutils-devel@sourceware.org \
    --cc=mark@klomp.org \
    --cc=quic_apinski@quicinc.com \
    --cc=sidneym@quicinc.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).