From: Nick Clifton <nickc@redhat.com>
To: Binutils <binutils@sourceware.org>
Subject: A GNU Binutils wiki
Date: Tue, 1 Nov 2022 13:34:12 +0000 [thread overview]
Message-ID: <71067e2b-f43b-2be8-ea4a-88ead1dd6e56@redhat.com> (raw)
Hi Guys,
I am in the process of creating a wiki for the binutils:
https://sourceware.org/binutils/wiki/HomePage
It is still bare bones at the moment, but I am hoping to build it
up over time. Actually to be honest I am hoping that all of us
will help to build it up over time.
This was inspired by some conversations and talks at this year's
GNU Tools Cauldron. The intent is to provide a site for helping
newcomers and experts alike with using and contributing to the
GNU binutils. Ideally attracting new contributors in the process
and making it easier for existing contributors to get their
patches approved and committed.
The wiki is hosted on the sourceware site, but I do not know if
this means that people with write permission for the git repository
can also edit the wiki directly. If not, or if anyone without
write permission also wants to contribute, then I am sure that a
quick email to the overseers will sort things out.
Cheers
Nick
next reply other threads:[~2022-11-01 13:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 13:34 Nick Clifton [this message]
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
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=71067e2b-f43b-2be8-ea4a-88ead1dd6e56@redhat.com \
--to=nickc@redhat.com \
--cc=binutils@sourceware.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).