aboutsummaryrefslogtreecommitdiff
path: root/README-hacking
diff options
context:
space:
mode:
authorDmitry V. Levin <ldv@strace.io>2024-10-14 08:00:00 +0000
committerDmitry V. Levin <ldv@strace.io>2024-10-23 08:00:00 +0000
commit613e59dca7034168bab4b9f6a89dd864957f0426 (patch)
tree70111f765659715d29c91421ed06d0847d2c496a /README-hacking
parent4aa31119988c4dcceaa9edce74121d2c057ad1f8 (diff)
downloadpam-613e59dca7034168bab4b9f6a89dd864957f0426.tar.gz
pam-613e59dca7034168bab4b9f6a89dd864957f0426.tar.bz2
pam-613e59dca7034168bab4b9f6a89dd864957f0426.zip
build: drop autotools support
There is no point in supporting two different build systems.
Diffstat (limited to 'README-hacking')
-rw-r--r--README-hacking17
1 files changed, 0 insertions, 17 deletions
diff --git a/README-hacking b/README-hacking
deleted file mode 100644
index d3700943..00000000
--- a/README-hacking
+++ /dev/null
@@ -1,17 +0,0 @@
-No more ChangeLog file
-======================
-Do not create or modify the ChangeLog files. Starting at 2011-10-26, the
-policy changed. Before, we would insert the exact same text (or worse,
-sometimes slightly differing) into both the ChangeLog file and the commit
-log. Now we put that information only in the commit log, and generate
-the ChangeLog file from logs at "make dist" time. As such, there are
-strict requirements on the form of the commit log messages.
-
-
-Commit log requirements
-=======================
-Each commit log should always start with a one-line summary, the second
-line should be blank, and the remaining lines are usually ChangeLog-style
-entries for all affected files, except the leading TABs which should
-be omitted. It's OK to write a few lines of prose describing the change,
-when the summary and ChangeLog entries don't give enough of the big picture.