public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Nick Clifton <nickc@redhat.com>
Cc: joel@rtems.org, Mike Frysinger <vapier@gentoo.org>,
	Joel Brobecker <brobecker@adacore.com>,
	Nick Clifton via Binutils <binutils@sourceware.org>
Subject: Re: A GNU Binutils wiki
Date: Wed, 2 Nov 2022 08:04:20 -0700	[thread overview]
Message-ID: <Y2KG9BTkSGnAOcv2@adacore.com> (raw)
In-Reply-To: <87fb1712-d568-46fc-aa47-733ff6931171@redhat.com>

> > Sorry to be negative. I like the "control" in source code control
> > and a wiki is lacking there.
> 
> That's fine.  It is good to have an opinion and I am glad that you
> are willing to express it.  My counter would be - what can we do instead ?
> 
> I know that most of the information intended for the wiki can be found
> by digging through the sources, but that will not work for people who
> are not already deeply familiar with the binutils.  So I wanted to create
> a place where people with at least some experience with other part(s) of
> the GNU toolchain would expect to be able to find information on the
> binutils.
> 
> Plus I wanted to provide a location for binutils users and contributor to
> be able to provide their own content.  Descriptions of the problems that
> they encountered whilst porting the binutils; advice for users of small
> devices that need custom linker scripts in order to work properly and so
> on.
> 
> Plus a location with responses to frequently asked questions(tm) which we
> can use when answering those I-have-found-a-name-mangling-bug and
> why-doesn't-the-assembler-auto-correct-my-bugs type questions on the
> mailing list.

To have perfect documentation, we'd need someone willing to act as
its curator, and that's a big job, no matter what technology you use.

FWIW I do feel that the wiki has been a positive addition for GDB.
While it hasn't been perfect, it has has lowered the barrier for
contributing changes to this part of the project's documentation.
We have had contributions from users who normally do not contribute
to the GDB project itself as well.

-- 
Joel

  reply	other threads:[~2022-11-02 15:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-01 13:34 Nick Clifton
2022-11-01 13:44 ` Joel Brobecker
2022-11-01 15:17   ` Mike Frysinger
2022-11-01 16:47     ` Nick Clifton
2022-11-02 10:34       ` Mike Frysinger
2022-11-02 13:41         ` Joel Sherrill
2022-11-02 14:49           ` Nick Clifton
2022-11-02 15:04             ` Joel Brobecker [this message]
2022-11-02 15:12             ` Joel Sherrill
2022-11-27 23:44             ` Mark Wielaard
2022-11-30 11:03               ` Nick Clifton
2022-12-31 22:19                 ` Mark Wielaard
2023-01-03 10:08                   ` Nick Clifton
2022-11-02 15:28           ` Luis Machado
2022-11-09 17:00             ` Mike Frysinger

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=Y2KG9BTkSGnAOcv2@adacore.com \
    --to=brobecker@adacore.com \
    --cc=binutils@sourceware.org \
    --cc=joel@rtems.org \
    --cc=nickc@redhat.com \
    --cc=vapier@gentoo.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).