FreeChainXenon/binutils-gdb
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

* CONTRIBUTE: Update.

Browse source
This commit is contained in:
Andrew Cagney 2001-09-26 20:52:56 +00:00
parent 1fd716b9b2
commit ff1da24e18
2 changed files with 20 additions and 46 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

62
gdb/CONTRIBUTE
View file

@ -21,7 +21,7 @@ package. We welcome all of the above and feel free to ask on the GDB
mailing lists if you are looking for feedback or for people to review mailing lists if you are looking for feedback or for people to review
a work in progress. a work in progress.
Ref: http://sourceware.cygnus.com/gdb Ref: http://www.gnu.org/software/gdb/
Finally, there are certain legal requirements and style issues which Finally, there are certain legal requirements and style issues which
all contributors need to be aware of. all contributors need to be aware of.
@ -29,58 +29,29 @@ all contributors need to be aware of.
o Coding Standards o Coding Standards
All contributions must conform to the GNU Coding Standard. All contributions must conform to the GNU Coding Standard.
http://www.gnu.ai.mit.edu/prep/standards_toc.html
Submissions which do not conform to the standards will be Submissions which do not conform to the standards will be
returned with a request to reformat the changes. returned with a request to reformat the changes.
For GDB, that standard is more tightly defined. GDB's GDB has certain additional coding requirements. Those
coding standard is determined by the output of requirements are explained in the GDB internals documentation
gnu-indent. in the gdb/doc directory.
This situation came about because, by the start of '99, Ref: http://www.gnu.org/prep/standards_toc.html
GDB's coding style was so bad an inconsistent that it was
decided to restart things from scratch.
o Copyright Assignment o Copyright Assignment
There are certain legal requirements
Before we can accept code contributions from you, we need a Before we can accept code contributions from you, we need a
copyright assignment form filled out. copyright assignment form filled out and filed with the FSF.
If you've developed some addition or patch to GDB that you See some documentation by the FSF for details and contact us
would like to contribute, you should fill out a copyright (either via the GDB mailing list or the GDB maintainer that is
assignment form and send it in to the FSF. We are unable to taking care of your contributions) to obtain the relevant
use code from you until this is on-file at the FSF, so get forms.
that paperwork in! This form covers one batch of changes.
Ref: http://gcc.gnu.org/fsf-forms/assignment-instructions.html
If you think you're going to be doing continuing work on GDB, it Small changes can be accepted without a copyright assignment form on file.
would be easier to use a different form, which arranges to
assign the copyright for all your future changes to GDB. It is
called assign.future. Please note that if you switch
employers, the new employer will need to fill out the
disclaim.future form; there is no need to fill out the
assign.future form again.
Ref: http://gcc.gnu.org/fsf-forms/assign.future
Ref: http://gcc.gnu.org/fsf-forms/disclaim.future
There are several other forms you can fill out for different Ref: http://www.gnu.org/prep/maintain.html#SEC6
circumstances (e.g. to contribute an entirely new program, to
contribute significant changes to a manual, etc.)
Ref: http://gcc.gnu.org/fsf-forms/copyrights.html
Small changes can be accepted without a copyright assignment
form on file.
This is pretty confusing! If you are unsure of what is
necessary, just ask the GDB mailing list and we'll figure out
what is best for you.
Note: Many of these forms have a place for "name of
program". Insert the name of one program in that place -- in
this case, "GDB".
o Submitting Patches o Submitting Patches
@ -98,11 +69,10 @@ o Submitting Patches
unlike some other projects, we do require ChangeLogs also for unlike some other projects, we do require ChangeLogs also for
documentation (i.e., .texi files). documentation (i.e., .texi files).
The patch itself. If you are accessing the CVS repository at: The patch itself. If you are accessing the CVS repository use
Cygnus, use "cvs update; cvs diff -c3p"; else, use "diff -c3p "cvs update; cvs diff -c3p"; else, use "diff -c3p OLD NEW" or
OLD NEW" or "diff -up OLD NEW". If your version of diff does "diff -up OLD NEW". If your version of diff does not support
not support these options, then get the latest version of GNU these options, then get the latest version of GNU diff.
diff.
We accept patches as plain text (preferred for the compilers We accept patches as plain text (preferred for the compilers
themselves), MIME attachments (preferred for the web pages), themselves), MIME attachments (preferred for the web pages),

4
gdb/ChangeLog
View file

@ -1,3 +1,7 @@
2001-09-26 Andrew Cagney <ac131313@redhat.com>
* CONTRIBUTE: Update.
2001-09-26 Kevin Buettner <kevinb@redhat.com> 2001-09-26 Kevin Buettner <kevinb@redhat.com>
* solib-svr4.h (set_solib_svr4_fetch_link_map_offsets): Add * solib-svr4.h (set_solib_svr4_fetch_link_map_offsets): Add