.cvsignore: add more files
clean.sh: don't recurse into SCM directories
tools-for-build/canonicalize-whitespace: use more generic option to
check expand utility to make non-GNU expand happy
tools-for-build/whitespacely-canonical-filenames: add more SCM directories
# test-passed
# generated by automatic directory-test-thyself procedure
find . \( \
+ -name _darcs -o \
+ -name '{arch}' -o \
+ -name CVS -o \
+ -name .hg -o \
+ -name .svn \) -type d -prune -o \
+ \( \
-type l -o \
-name '*~' -o \
-name '#*#' -o \
{
struct futex *futex = (struct futex *)p;
int ret, count;
-
+
ret = pthread_mutex_lock(&futex_lock);
futex_assert(ret == 0);
stack-alignment-offset
test-status.lisp-expr
run-program-ed-test.tmp
+threads-foreign.c
# Convert tabs to spaces and delete trailing whitespace in files
# which we can safely assume to be source files in appropriate languages.
-if ! expand --version < $DEVNULL
+if ! expand -t 8 < $DEVNULL
then
# If we're building with MSYS on Windows GNU expand is not available,
# and what we get is Microsoft Expand, which is something quite different,
# ?
for source_extension in $source_extensions; do
- find . -name _darcs -prune -o \
- -name '{arch}' -prune -o \
+ find . \( \
+ -name _darcs -o \
+ -name '{arch}' -o \
+ -name CVS -o \
+ -name .hg -o \
+ -name .svn \) -type d -prune -o \
-name '*'$source_extension -print
done
;;; checkins which aren't released. (And occasionally for internal
;;; versions, especially for internal versions off the main CVS
;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
-"1.0.0.32"
+"1.0.0.33"