public inbox for jit@gcc.gnu.org
 help / color / mirror / Atom feed
From: Guillaume Gomez <guillaume1.gomez@gmail.com>
To: Antoni Boucher <bouanto@zoho.com>
Cc: gcc-patches@gcc.gnu.org, jit@gcc.gnu.org
Subject: Re: [PATCH] libgccjit: Fix a failing test
Date: Thu, 5 Jan 2023 23:37:53 +0100	[thread overview]
Message-ID: <CAAOQCfTLU5P1R7Fmayjaxx+LdWRbpDKm7o0ARHAJg1w2bmiVLA@mail.gmail.com> (raw)
In-Reply-To: <CAAOQCfTEdKFYjuo=C7Rw26AjBvbsuA6ZTDAY9GcsrApEFsS1cg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 792 bytes --]

Ping David.

Le sam. 24 déc. 2022 à 21:01, Guillaume Gomez <guillaume1.gomez@gmail.com>
a écrit :

> Ping David
>
> Le jeu. 15 déc. 2022 à 11:34, Guillaume Gomez <guillaume1.gomez@gmail.com>
> a écrit :
>
>> Forgot it indeed, thanks for notifying me!
>>
>> I modified the commit message to add it and added it into this email.
>>
>> Le mer. 14 déc. 2022 à 16:12, Antoni Boucher <bouanto@zoho.com> a écrit :
>>
>>> Thanks!
>>>
>>> In your patch, you're missing this line at the end of the commit
>>> message:
>>>
>>>    Signed-off-by: Guillaume Gomez <guillaume1.gomez@gmail.com>
>>>
>>> On Wed, 2022-12-14 at 14:39 +0100, Guillaume Gomez via Jit wrote:
>>> > Hi,
>>> >
>>> > This fixes bug 107999.
>>> >
>>> > Thanks in advance for the review.
>>>
>>>

  reply	other threads:[~2023-01-05 22:38 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14 13:39 Guillaume Gomez
2022-12-14 15:12 ` Antoni Boucher
2022-12-15  7:34   ` Guillaume Gomez
2022-12-24 20:01     ` Guillaume Gomez
2023-01-05 22:37       ` Guillaume Gomez [this message]
2023-01-16 14:08         ` Guillaume Gomez
2023-03-02 19:41           ` Guillaume Gomez
2023-03-02 21:58     ` David Malcolm
2023-03-02 22:19       ` Guillaume Gomez
2023-03-02 22:29         ` Guillaume Gomez
2023-03-02 22:33           ` David Malcolm
2023-03-02 22:35             ` Guillaume Gomez
2023-03-02 22:54               ` David Malcolm
2023-03-03  9:31                 ` Guillaume Gomez

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=CAAOQCfTLU5P1R7Fmayjaxx+LdWRbpDKm7o0ARHAJg1w2bmiVLA@mail.gmail.com \
    --to=guillaume1.gomez@gmail.com \
    --cc=bouanto@zoho.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jit@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).