What is the rationale for having --no-timestamps in QUILT_DIFF_ARGS and QUILT_REFRESH_ARGS by default? I understand that quilt itself will touch the timestamp of the files, but even then, these timestamps seem to have some value.
Would there be an objection to changing the default to timestamps enabled? --- quilt.changes | 5 +++++ quilt.quiltrc | 8 ++++++-- 2 files changed, 11 insertions(+), 2 deletions(-) --- a/quilt.changes +++ b/quilt.changes @@ -1,4 +1,9 @@ ------------------------------------------------------------------- +Wed Nov 4 15:25:04 CET 2009 - [email protected] + +- quilt.quiltrc: Include timestamps in patches by default. + +------------------------------------------------------------------- Mon Nov 2 20:12:31 CET 2009 - [email protected] - Implement -r / --reference option in compat/date (patch from --- a/quilt.quiltrc +++ b/quilt.quiltrc @@ -13,11 +13,15 @@ QUILT_PATCH_OPTS="--unified" # Options to pass to commands (QUILT_${COMMAND}_ARGS) QUILT_PUSH_ARGS="--color=auto" -QUILT_DIFF_ARGS="--no-timestamps --color=auto" -QUILT_REFRESH_ARGS="--no-timestamps --backup" +QUILT_DIFF_ARGS="--color=auto" +QUILT_REFRESH_ARGS="--backup" QUILT_SERIES_ARGS="--color=auto" QUILT_PATCHES_ARGS="--color=auto" +# Fine tuning of patch format +#QUILT_NO_DIFF_INDEX=1 +#QUILT_NO_DIFF_TIMESTAMP=1 + # (Add "-p ab" to QUILT_DIFF_ARGS and QUILT_REFRESH_ARGS to get # -p1 style diffs with a/file and b/file filenams in headers # instead of dir.orig/file and dir/file.) -- Jean Delvare Suse L3 _______________________________________________ Quilt-dev mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/quilt-dev
