From 554fd8c5195424bdbcabf5de30fdc183aba391bd Mon Sep 17 00:00:00 2001 From: upstream source tree Date: Sun, 15 Mar 2015 20:14:05 -0400 Subject: obtained gcc-4.6.4.tar.bz2 from upstream website; verified gcc-4.6.4.tar.bz2.sig; imported gcc-4.6.4 source tree from verified upstream tarball. downloading a git-generated archive based on the 'upstream' tag should provide you with a source tree that is binary identical to the one extracted from the above tarball. if you have obtained the source via the command 'git clone', however, do note that line-endings of files in your working directory might differ from line-endings of the respective files in the upstream repository. --- gcc/doc/contribute.texi | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) create mode 100644 gcc/doc/contribute.texi (limited to 'gcc/doc/contribute.texi') diff --git a/gcc/doc/contribute.texi b/gcc/doc/contribute.texi new file mode 100644 index 000000000..55049f1b7 --- /dev/null +++ b/gcc/doc/contribute.texi @@ -0,0 +1,25 @@ +@c Copyright (C) 1988, 1989, 1992, 1993, 1994, 1995, 1996, 1997, 1998, +@c 1999, 2000, 2001, 2004, 2006 Free Software Foundation, Inc. +@c This is part of the GCC manual. +@c For copying conditions, see the file gcc.texi. + +@node Contributing +@chapter Contributing to GCC Development + +If you would like to help pretest GCC releases to assure they work well, +current development sources are available by SVN (see +@uref{http://gcc.gnu.org/svn.html}). Source and binary snapshots are +also available for FTP; see @uref{http://gcc.gnu.org/snapshots.html}. + +If you would like to work on improvements to GCC, please read the +advice at these URLs: + +@smallexample +@uref{http://gcc.gnu.org/contribute.html} +@uref{http://gcc.gnu.org/contributewhy.html} +@end smallexample + +@noindent +for information on how to make useful contributions and avoid +duplication of effort. Suggested projects are listed at +@uref{http://gcc.gnu.org/projects/}. -- cgit v1.2.3