blob: 16d12c0316a55f6ef1943632fa5dc9d1b274b272 [file] [log] [blame]
Dmitry V. Levin08f922a2009-07-09 00:47:41 +00001Requirements
2============
Dmitry V. Levin82f4cc62009-07-07 22:33:41 +00003If you use the GIT version of strace there will be some files missing
Roland McGrath6d2b3492002-12-30 00:51:30 +00004that you need to build strace. These files are generated by tools from
Mike Frysinger600eafb2015-03-02 20:42:04 -05005the GNU Autoconf and Automake packages.
6
7Note: rather than run `autoreconf' directly, use the `./bootstrap' script.
Dmitry V. Levin08f922a2009-07-09 00:47:41 +00008
9
10No more ChangeLog file
11======================
12Do not create or modify the ChangeLog files. Starting at 2009-07-09, the
13policy changed. Before, we would insert the exact same text (or worse,
14sometimes slightly differing) into both the ChangeLog file and the commit
15log. Now we put that information only in the commit log, and generate
16the top-level ChangeLog file from logs at "make dist" time. As such,
17there are strict requirements on the form of the commit log messages.
18
19
20Commit log requirements
21=======================
22Each commit log should always start with a one-line summary, the second
23line should be blank, and the remaining lines are usually ChangeLog-style
24entries for all affected files, except the leading TABs which should
25be omitted.
Dmitry V. Levin5700f682012-05-03 01:44:49 +000026
27
28Documentation
29=============
30All noteworthy changes should be mentioned in NEWS. All changes in strace
31command interface should be reflected in the man page. New options should
32be documented both in -h output and in the man page.