public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Dmitry Neverov <dmitry.neverov@jetbrains.com>,
	Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org, Joel Brobecker <brobecker@adacore.com>
Subject: Re: [RFC v2][PR symtab/30520] gdb/symtab: fix the gdb.cp/anon-struct test
Date: Fri, 3 May 2024 18:20:07 -0700	[thread overview]
Message-ID: <ZjWNRyMCd1uvlBMX@adacore.com> (raw)
In-Reply-To: <87edc2rx9d.fsf@tromey.com>

Hi Dmitry (hey Tom),

Any news on the copyright assignment side? We're getting closer to
being ready for GDB 15 branching, and soon after that for GDB 15.1
release. If we haven't heard from them in a while, I think it would
be worth explaining to them that we're block on this, and that
if we can't get the assignment papers through soon, it'll me we'll
have to ship 15.1 without this enhancement, which would be a real
shame.

On Fri, Mar 22, 2024 at 11:29:02AM -0600, Tom Tromey wrote:
> >>>>> "Dmitry" == Dmitry Neverov <dmitry.neverov@jetbrains.com> writes:
> 
> >> Do you know the current status of it?
> >> Unfortunately we can't accept the patches without it.
> 
> Dmitry> I've sent all the papers, but we had a typo in a disclaimer, so
> Dmitry> I'm back to getting them fixed and signed. Hope it will be
> Dmitry> faster than the first round.
> 
> If this is definitely happening (like it wasn't completely derailed for
> some reason) then IMO it's fine to update the patches and re-send them.
> That might hasten their landing once the paperwork is done.

FWIW, that's an excellent idea. Any chance we could have those
submitted, and hopefully approved soon after?

Thank you!
-- 
Joel

  reply	other threads:[~2024-05-04  1:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-23 17:03 [RFC v2][PR symtab/30520 1/4] gdb/symtab: check name matches before expanding a CU Dmitry Neverov
2024-01-23 17:03 ` [RFC v2][PR symtab/30520 2/4] gdb/symtab: reuse last segment lookup name info Dmitry Neverov
2024-01-23 17:03 ` [RFC v2][PR symtab/30520 3/4] gdb/symtab: compute match_type outside the loop Dmitry Neverov
2024-01-23 17:03 ` [RFC v2][PR symtab/30520 4/4] gdb/symtab: use symbol name matcher for all segments in a qualified name Dmitry Neverov
2024-01-25  8:44 ` [RFC v2][PR symtab/30520] gdb/symtab: fix the gdb.cp/anon-struct test Dmitry Neverov
2024-02-07 20:25   ` Tom Tromey
2024-02-09 16:32     ` Dmitry Neverov
2024-02-09 19:38       ` Tom Tromey
2024-03-18 16:35         ` Dmitry Neverov
2024-03-18 17:58           ` Tom Tromey
2024-03-19 12:16             ` Dmitry Neverov
2024-03-22 17:29               ` Tom Tromey
2024-05-04  1:20                 ` Joel Brobecker [this message]
2024-05-06 14:32                   ` Dmitry Neverov

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=ZjWNRyMCd1uvlBMX@adacore.com \
    --to=brobecker@adacore.com \
    --cc=dmitry.neverov@jetbrains.com \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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).