From: Sahil <icegambit91@gmail.com>
To: Guinevere Larsen <blarsen@redhat.com>, Eli Zaretskii <eliz@gnu.org>
Cc: gdb-patches@sourceware.org, sahilcdq@proton.me
Subject: Re: [PATCH v3] gdb: fix "frame function" failure to get frame when call is it's last instruction
Date: Sat, 06 Jul 2024 14:14:49 +0530 [thread overview]
Message-ID: <5797530.DvuYhMxLoT@valdaarhun> (raw)
In-Reply-To: <8634on7lgw.fsf@gnu.org>
Hi,
On Friday, July 5, 2024 8:08:11 PM GMT+5:30 Guinevere Larsen wrote:
> [...]
> If you have completed the copyright assignment process, yes that's
> exactly it. If you haven't, you'll need that finished before being
> allowed to push, since I think the changes to the testcase would be
> considered legally significant.
On Friday, July 5, 2024 11:46:47 PM GMT+5:30 Eli Zaretskii wrote:
> > Date: Fri, 5 Jul 2024 11:38:11 -0300
> > Cc: Sahil Siddiq <sahilcdq@proton.me>,
> >
> > "Eli Zaretskii (eliz@gnu.org)" <eliz@gnu.org>
> >
> > From: Guinevere Larsen <blarsen@redhat.com>
> >
> > I'm not sure if you should start the assignment process yet, since the
> > patch hasn't been approved. Eli (CC'd because of this question), should
> > Sahil start the assignment process already, or wait for someone to
> > approve their patch first?
>
> Sahil can start the process regardless of the approval. The copyright
> assignment is for this and all the future contributions, so even if
> this one eventually doesn't go in, the assignment is good and valid
> for future ones.
Thank you for the clarifications. I'll start the process.
Regards,
Sahil
next prev parent reply other threads:[~2024-07-06 8:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 16:33 Sahil Siddiq
2024-07-05 13:06 ` Guinevere Larsen
2024-07-05 14:23 ` Sahil
2024-07-05 14:38 ` Guinevere Larsen
2024-07-05 18:16 ` Eli Zaretskii
2024-07-06 8:44 ` Sahil [this message]
2025-10-22 17:50 ` Tom Tromey
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=5797530.DvuYhMxLoT@valdaarhun \
--to=icegambit91@gmail.com \
--cc=blarsen@redhat.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=sahilcdq@proton.me \
/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