aboutsummaryrefslogtreecommitdiff
path: root/src/util
diff options
context:
space:
mode:
authorTom Yu <tlyu@mit.edu>2016-08-31 13:40:22 -0400
committerTom Yu <tlyu@mit.edu>2016-09-09 13:00:39 -0400
commit9c18f6c93b602ec69ca2640e27ab2ccbb7f45a3c (patch)
tree067239535d8db8e1240d6b0ea64dc9daa7c54ccc /src/util
parentf60ac0e5256d9a4006688b0e1c5cc8caf7c9d2b3 (diff)
downloadkrb5-9c18f6c93b602ec69ca2640e27ab2ccbb7f45a3c.zip
krb5-9c18f6c93b602ec69ca2640e27ab2ccbb7f45a3c.tar.gz
krb5-9c18f6c93b602ec69ca2640e27ab2ccbb7f45a3c.tar.bz2
Stop generating doc/CHANGES
Shipping a 10MB+ doc/CHANGES file in the release tarball doesn't make much sense in a modern context where historical information is readily available in a distributed version control system. ticket: 8488 (new)
Diffstat (limited to 'src/util')
-rwxr-xr-xsrc/util/mkrel3
1 files changed, 0 insertions, 3 deletions
diff --git a/src/util/mkrel b/src/util/mkrel
index 6223cf1..d962a64 100755
--- a/src/util/mkrel
+++ b/src/util/mkrel
@@ -136,9 +136,6 @@ if test $newstyle = t; then
sed -e '/#[a-z ]*KRB5_RELDATE/c\
#define KRB5_RELDATE "'"$reldate"'"' patchlevel.h > patchlevel.h.new && \
mv patchlevel.h.new patchlevel.h)
- if test $checkout = t; then
- (cd $reldir && git log --stat $reltag > doc/CHANGES)
- fi
else
(cd $reldir/src/lib/krb5/krb && \