public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Alexandre Oliva <oliva@adacore.com>
Cc: gcc-patches@gcc.gnu.org, Tom Tromey <tromey@adacore.com>,
	Jason Merrill <jason@redhat.com>,
	Cary Coutant <ccoutant@gmail.com>,
	Jakub Jelinek <jakub@redhat.com>,
	David Edelsohn <dje.gcc@gmail.com>, Kewen Lin <linkw@gcc.gnu.org>
Subject: Re: [PATCH v3 #1/2] enable adjustment of return_pc debug attrs
Date: Tue, 28 May 2024 15:24:34 -0500	[thread overview]
Message-ID: <20240528202434.GS19790@gate.crashing.org> (raw)
In-Reply-To: <orzfse9jl6.fsf_-_@lxoliva.fsfla.org>

On Sat, May 25, 2024 at 09:12:05AM -0300, Alexandre Oliva wrote:
<snip>

You sent multiple patch series in one thread, and multiple versions of
the same series even.

This is very hard to even *read*, let alone work with.  Please don't.


Segher

  parent reply	other threads:[~2024-05-28 20:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-23  3:12 [PATCH v2 " Alexandre Oliva, Alexandre Oliva
2023-03-23  3:15 ` [PATCH v2 #2/2] [rs6000] adjust " Alexandre Oliva
2023-04-14 14:12 ` [PATCH v2 #1/2] enable adjustment of " Alexandre Oliva
2023-04-27  9:40   ` Alexandre Oliva
2024-05-25 12:12     ` [PATCH v3 " Alexandre Oliva
2024-05-28 19:16       ` Jason Merrill
2024-06-07  5:17         ` Alexandre Oliva
2024-05-28 20:24       ` Segher Boessenkool [this message]
2024-05-25 12:13     ` [PATCH v3 #1/2] [rs6000] adjust " Alexandre Oliva
2024-05-27  3:23       ` Kewen.Lin
2024-05-29  6:52         ` Alexandre Oliva
2024-05-30 18:18           ` Segher Boessenkool
2024-05-31  7:01           ` Kewen.Lin
2024-05-28 21:10       ` Segher Boessenkool
2024-05-30 16:40         ` [PATCH v3 #2/2] " Alexandre Oliva
2024-05-30 18:46           ` Segher Boessenkool

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=20240528202434.GS19790@gate.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=ccoutant@gmail.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jakub@redhat.com \
    --cc=jason@redhat.com \
    --cc=linkw@gcc.gnu.org \
    --cc=oliva@adacore.com \
    --cc=tromey@adacore.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).