From: Pedro Alves <palves@redhat.com>
To: Alan Hayward <Alan.Hayward@arm.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: nd <nd@arm.com>
Subject: Re: [PATCH] Replace contribution list in CONTRIBUTE file with wiki link
Date: Wed, 23 Jan 2019 16:03:00 -0000 [thread overview]
Message-ID: <79e6aeb8-fd9d-7269-ea6c-929812fd6f71@redhat.com> (raw)
In-Reply-To: <20190123094558.58854-1-alan.hayward@arm.com>
On 01/23/2019 09:46 AM, Alan Hayward wrote:
> +https://sourceware.org/gdb/wiki/ContributionChecklist
I'd rather point at https://sourceware.org/gdb/contribute/
and then have _that_ point at some page in the wiki.
That's what I had suggested in the other thread.
The reason is that the <https://sourceware.org/gdb/contribute/>
URL is going to be more stable than a wiki link, which we can
rename, split, etc. a bit more freely. The contribution checklist page
is quite large by now, and I've heard of people wishing for a smaller more
concise entry point. The checklist was meant to be that, a checklist.
A "how to contribute" page may have some higher level info to
get people started.
Thanks,
Pedro Alves
next prev parent reply other threads:[~2019-01-23 16:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-23 9:46 Alan Hayward
2019-01-23 15:21 ` Simon Marchi
2019-01-23 16:03 ` Pedro Alves [this message]
2019-01-23 17:15 ` Alan Hayward
2019-01-24 13:00 ` Pedro Alves
2019-01-25 6:08 ` Joel Brobecker
2019-01-25 14:30 ` Alan Hayward
[not found] ` <e9019e9b-f57b-26e8-1d53-2736798787e0@redhat.com>
2019-01-26 6:26 ` Joel Brobecker
2019-01-28 10:02 ` Alan Hayward
2019-01-28 19:50 ` Pedro Alves
2019-01-29 5:33 ` Joel Brobecker
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=79e6aeb8-fd9d-7269-ea6c-929812fd6f71@redhat.com \
--to=palves@redhat.com \
--cc=Alan.Hayward@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=nd@arm.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