Build Update for apache/httpd
-------------------------------------
Build: #1118
Status: Broken
Duration: 20 mins and 5 secs
Commit: ed119f2 (2.4.x)
Author: Ruediger Pluem
Message: Merge r1879822, r1879831, r1879840 from trunk:
Add a new way to document changes
* Makefile.in: Define the update-changes target to merge the change files
from the changes directory to the top of the CHANGES file and remove
them afterwards. If a Subversion binary was found during configure try
to svn rm them otherwise just delete them.
* configure.in: Search for the Subversion binary.
* acinclude.m4: Set the corresponding Makefile variable for the Subversion
binary.
* README.CHANGES: New file to document the new approach.
Can we have mercy with people working on case-preserving file systems?
Consider case insensitive filessystems
Consider case insensitive filessystems and thus choose a new non conflicting
name for the directory to store CHANGES entries.
Reviewed by: rpluem, jim, jorton
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1881728 13f79535-47bb-0310-9956-ffa450edef68
View the changeset: https://github.com/apache/httpd/compare/e006a6d8c163...ed119f2f8f0b
View the full build log and details: https://travis-ci.org/github/apache/httpd/builds/727281612?utm_medium=notification&utm_source=email
--
You can unsubscribe from build emails from the apache/httpd repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=69847&utm_medium=notification&utm_source=email.
Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email.
Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.
-------------------------------------
Build: #1118
Status: Broken
Duration: 20 mins and 5 secs
Commit: ed119f2 (2.4.x)
Author: Ruediger Pluem
Message: Merge r1879822, r1879831, r1879840 from trunk:
Add a new way to document changes
* Makefile.in: Define the update-changes target to merge the change files
from the changes directory to the top of the CHANGES file and remove
them afterwards. If a Subversion binary was found during configure try
to svn rm them otherwise just delete them.
* configure.in: Search for the Subversion binary.
* acinclude.m4: Set the corresponding Makefile variable for the Subversion
binary.
* README.CHANGES: New file to document the new approach.
Can we have mercy with people working on case-preserving file systems?
Consider case insensitive filessystems
Consider case insensitive filessystems and thus choose a new non conflicting
name for the directory to store CHANGES entries.
Reviewed by: rpluem, jim, jorton
git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1881728 13f79535-47bb-0310-9956-ffa450edef68
View the changeset: https://github.com/apache/httpd/compare/e006a6d8c163...ed119f2f8f0b
View the full build log and details: https://travis-ci.org/github/apache/httpd/builds/727281612?utm_medium=notification&utm_source=email
--
You can unsubscribe from build emails from the apache/httpd repository going to https://travis-ci.org/account/preferences/unsubscribe?repository=69847&utm_medium=notification&utm_source=email.
Or unsubscribe from *all* email updating your settings at https://travis-ci.org/account/preferences/unsubscribe?utm_medium=notification&utm_source=email.
Or configure specific recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications.