Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi <simon.marchi@ericsson.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 15:21:00 -0000	[thread overview]
Message-ID: <9b8f7f1c-e125-25dd-8f20-fab608bcda84@ericsson.com> (raw)
In-Reply-To: <20190123094558.58854-1-alan.hayward@arm.com>

On 2019-01-23 4:46 a.m., Alan Hayward wrote:
> The GDB wiki page has a much better contribution checklist than
> that in the GDB CONTRIBUTE file.  In addition, the wiki is easier
> to keep up to date with current processes.
> 
> Reduce the CONTRIBUTE file down to two short paragraphs with links
> to both the contribution process and the GDB homepage.  This also
> ensures anyone reading the CONTRIBUTE file for a given release has
> access to the latest processes.
> 
> gdb/ChangeLog:
> 
> 2019-01-23  Alan Hayward  <alan.hayward@arm.com>
> 
> 	* CONTRIBUTE: Replace contribution list with wiki link.
> ---
>  gdb/CONTRIBUTE | 147 +++++--------------------------------------------
>  1 file changed, 14 insertions(+), 133 deletions(-)
> 
> diff --git a/gdb/CONTRIBUTE b/gdb/CONTRIBUTE
> index 30f51ccdc7..e9a96e59bf 100644
> --- a/gdb/CONTRIBUTE
> +++ b/gdb/CONTRIBUTE
> @@ -4,142 +4,23 @@
>  GDB is a collaborative project and one which wants to encourage new
>  development.  You may wish to fix GDB bugs, improve testing, port GDB
>  to a new platform, update documentation, add new GDB features, and the
> -like. To help with this, there is a lot of documentation
> -available.. In addition to the user guide and internals manual
> -included in the GDB distribution, the GDB web pages also contain much
> -information.
> +like.  To help with this, there is a lot of documentation available.
> +In addition to the user guide and internals manual included in the GDB
> +distribution, the GDB web pages also contain much information.
>  
>  You may also want to submit your change so that can be considered for
> -conclusion in a future version of GDB (see below).  Regardless, we
> -encourage you to distribute the change yourself.
> +conclusion in a future version of GDB.  For a full guide on how to
> +submit patches see:

Is it just me, or the "You may also..." sentence is very weird?  conclusion
or inclusion?  There seems to be a missing work after "so that".

Otherwise, this LGTM, thanks.

Simon

  reply	other threads:[~2019-01-23 15:21 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 [this message]
2019-01-23 16:03 ` Pedro Alves
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=9b8f7f1c-e125-25dd-8f20-fab608bcda84@ericsson.com \
    --to=simon.marchi@ericsson.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