summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorStefano Lattarini <stefano.lattarini@gmail.com>2012-01-25 10:09:17 +0100
committerStefano Lattarini <stefano.lattarini@gmail.com>2012-01-25 10:10:24 +0100
commit5060920b1390bedaef7c0a4269b306bf7fa19799 (patch)
tree8d4e0d79a8baa89918864df20e07031c3f892102 /HACKING
parentbff57e68f5376806e75ef004708dbd76a5540f58 (diff)
downloadautomake-5060920b1390bedaef7c0a4269b306bf7fa19799.tar.gz
hacking: update advice w.r.t. synced files
* HACKING: Update and improve advices and explanations about files in the automake repository that are now owned by automake, but mirrored from other upstreams. Also, don't list these files explicitly, rather point the reader to the $(FETCHFILES) variable in Makefile.am. * Makefile.am (FETCHFILES): Don't state that "there should be a lot more here", as this is not true anymore today. Only 'COPYING' must be synced by hand.
Diffstat (limited to 'HACKING')
-rw-r--r--HACKING14
1 files changed, 7 insertions, 7 deletions
diff --git a/HACKING b/HACKING
index ed78c9f7d..26f1d91e4 100644
--- a/HACKING
+++ b/HACKING
@@ -27,13 +27,13 @@
sure to add a test case for it, and to reference such test case from
a proper Texinfo comment.
-* Some files in the automake package are not owned by automake. These
- files should never be edited here. These files are
- COPYING (from FSF),
- INSTALL (autoconf-patches@gnu.org),
- config.guess, config.sub (config-patches@gnu.org),
- texinfo.tex (bug-texinfo@gnu.org),
- Most of them are updated before release with `make fetch'.
+* Some files in the automake package are not owned by automake; these
+ files are listed in the $(FETCHFILES) variable in Makefile.am. They
+ should never be edited here. Almost all of them can be updated from
+ respective upstreams with "make fetch" (this should be done especially
+ before releases). The only exception is the 'lib/COPYING' (from FSF),
+ which should be updated by hand whenever the GPL gets updated (which
+ shouldn't happen that often anyway :-)
* Changes other than bug fixes must be mentioned in NEWS. Important
bug fixes should be mentioned in NEWS, too.