[patch] gdb/CONTRIBUTE update

[Jan Kratochvil <jan.kratochvil@redhat.com>]

Hi Eli,

there is one s/conclusion/inclusion/ fix reviewed by Phil.

Otherwise TBH I did not well understand the "distribute the change yourself"
encouragement, it seems to me like a suggestion one should keep 3rd party
patches, these are discouraged, patches should be integrated to FSF GDB.

And added the new paragraph as people send patch and as they expect the GDB
maintainers will grab it and handle it on their own many patches get forgotten
that way as there is no patch tracking in place (yet).

Just such an idea, np if people consider it OK as is.


Thanks,
Jan


gdb/
2013-02-21  Jan Kratochvil  <jan.kratochvil@redhat.com>

	* CONTRIBUTE: Fix type to inclusion.  Extend patches distribution
	description.  Add new paragraph on patch ownership.

diff --git a/gdb/CONTRIBUTE b/gdb/CONTRIBUTE
index cdec246..67af0ab 100644
--- a/gdb/CONTRIBUTE
+++ b/gdb/CONTRIBUTE
@@ -10,8 +10,9 @@ 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.
+inclusion in a future version of GDB (see below).  Regardless, we
+encourage you to distribute the change yourself until it gets integrated
+into FSF GDB mainline sources.
 
 If you don't feel up to hacking GDB, there are still plenty of ways to
 help!  You can answer questions on the mailing lists, write
@@ -86,6 +87,12 @@ o	Submitting Patches
 	CVS repository, see the Anonymous read-only CVS access and
 	Read-write CVS access page.
 
+	Patch from a contributor needs a review with approval from
+	maintainer.  Still you drive the review process and inclusion
+	process of the patch.  If there is no reply in a week send a new
+	mail (not reply) with PING in its subject.  Occasionally even
+	a PING^2 mail may be needed in another week of no replise.
+
 --
 
 Supplemental information for GDB: