public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org, aburgess@redhat.com
Subject: Re: [PATCH] gdb/doc: don't use @var on @defun lines
Date: Thu, 27 Apr 2023 20:09:31 +0300	[thread overview]
Message-ID: <83fs8ls14k.fsf@gnu.org> (raw)
In-Reply-To: <87y1mdw9y0.fsf@tromey.com> (message from Tom Tromey on Thu, 27 Apr 2023 10:45:27 -0600)

> From: Tom Tromey <tromey@adacore.com>
> Cc: Andrew Burgess <aburgess@redhat.com>,  Eli Zaretskii <eliz@gnu.org>
> Date: Thu, 27 Apr 2023 10:45:27 -0600
> 
> >> Given your feedback on other patches that @var on a @defun line is not
> >> desirable I assume I could probably push this as obvious?
> 
> Eli> Yes, thanks.
> 
> I also sent a patch like this, but my version fixed another issue:
> 
> https://sourceware.org/pipermail/gdb-patches/2023-April/198659.html
> 
> ... namely that one variable name seemed strange, as it is invalid in
> Python.
> 
> I can rebase that once Andrew's goes in.

Any such changes are obvious, thanks.

  reply	other threads:[~2023-04-27 17:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06 14:31 Andrew Burgess
2023-04-27 13:04 ` Andrew Burgess
2023-04-27 13:28   ` Eli Zaretskii
2023-04-27 16:45     ` Tom Tromey
2023-04-27 17:09       ` Eli Zaretskii [this message]
2023-04-28 14:07       ` Andrew Burgess
2023-04-28 16:52         ` 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=83fs8ls14k.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=aburgess@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --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).