public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Nick Clifton <nickc@redhat.com>
Cc: Binutils <binutils@sourceware.org>
Subject: Re: [PATCH] gas: accept custom ".linefile <n> ."
Date: Mon, 14 Nov 2022 17:16:26 +0100	[thread overview]
Message-ID: <05230a00-0302-c763-02a2-aff573582449@suse.com> (raw)
In-Reply-To: <5be45fcc-5e0b-22b8-c0bc-5055b4e50060@redhat.com>

On 14.11.2022 17:02, Nick Clifton wrote:
>>> We should document this behaviour in the as.texi file then, so that it
>>> is "official"...
>>
>> Do you really think we should? .linefile as a whole is undocumented. If
>> people use it, then at their own risk (if we made things "official",
>> later we couldn't later behavior anymore).
> 
> Alright - in which case we should document it as being unsupported/not
> for use.
> 
> I am just trying to avoid the situation where a future binutils user
> discovers the directive, tries it out and then complains about it not
> working as expected/documented/whatever.

Okay, if you could give me a hint where undocumented stuff is to go
in as.texi, I could see about making a patch. Otherwise if you would
make one, it could still educate me in case something else needs
similar treatment going forward.

Jan

  reply	other threads:[~2022-11-14 16:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-11  7:32 Jan Beulich
2022-11-14 13:43 ` Nick Clifton
2022-11-14 15:53   ` Jan Beulich
2022-11-14 16:02     ` Nick Clifton
2022-11-14 16:16       ` Jan Beulich [this message]
2022-11-15 11:16         ` Nick Clifton
2022-11-15  7:59   ` Jan Beulich
2022-11-15 11:23     ` Nick Clifton

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=05230a00-0302-c763-02a2-aff573582449@suse.com \
    --to=jbeulich@suse.com \
    --cc=binutils@sourceware.org \
    --cc=nickc@redhat.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).