Searched hist:1.911 (Results 1 - 25 of 26) sorted by relevance
| /src/usr.bin/make/unit-tests/ | ||
| H A D | deptgt-order.exp | 1.4 Tue Dec 28 15:49:00 GMT 2021 rillig make: make debug logging a bit more human-friendly The previous log format "ParseReadLine (%d): '%s'" focused on the implementation, it was not immediately obvious to a casual reader that the number in parentheses was the line number. Additionally, having both a colon and quotes in a log message is uncommon. The quotes have been added in parse.c 1.127 from 2007-01-01. The new log format "Parsing line %d: %s" is meant to be easier readable by humans. The quotes are not needed since ParseReadLine always strips trailing whitespace, leaving no room for ambiguities. The other log messages follow common punctuation rules, which makes the beginning of the line equally unambiguous. Before var.c 1.911 from 2021-04-05, variable assignments were logged with the format "%s:%s = %s", without a space after the colon. |
| H A D | suff-incomplete.exp | 1.6 Tue Dec 28 15:49:00 GMT 2021 rillig make: make debug logging a bit more human-friendly The previous log format "ParseReadLine (%d): '%s'" focused on the implementation, it was not immediately obvious to a casual reader that the number in parentheses was the line number. Additionally, having both a colon and quotes in a log message is uncommon. The quotes have been added in parse.c 1.127 from 2007-01-01. The new log format "Parsing line %d: %s" is meant to be easier readable by humans. The quotes are not needed since ParseReadLine always strips trailing whitespace, leaving no room for ambiguities. The other log messages follow common punctuation rules, which makes the beginning of the line equally unambiguous. Before var.c 1.911 from 2021-04-05, variable assignments were logged with the format "%s:%s = %s", without a space after the colon. |
| H A D | suff-rebuild.exp | 1.8 Tue Dec 28 15:49:00 GMT 2021 rillig branches: 1.8.4; make: make debug logging a bit more human-friendly The previous log format "ParseReadLine (%d): '%s'" focused on the implementation, it was not immediately obvious to a casual reader that the number in parentheses was the line number. Additionally, having both a colon and quotes in a log message is uncommon. The quotes have been added in parse.c 1.127 from 2007-01-01. The new log format "Parsing line %d: %s" is meant to be easier readable by humans. The quotes are not needed since ParseReadLine always strips trailing whitespace, leaving no room for ambiguities. The other log messages follow common punctuation rules, which makes the beginning of the line equally unambiguous. Before var.c 1.911 from 2021-04-05, variable assignments were logged with the format "%s:%s = %s", without a space after the colon. |
| H A D | include-main.exp | 1.8 Tue Dec 28 15:49:00 GMT 2021 rillig make: make debug logging a bit more human-friendly The previous log format "ParseReadLine (%d): '%s'" focused on the implementation, it was not immediately obvious to a casual reader that the number in parentheses was the line number. Additionally, having both a colon and quotes in a log message is uncommon. The quotes have been added in parse.c 1.127 from 2007-01-01. The new log format "Parsing line %d: %s" is meant to be easier readable by humans. The quotes are not needed since ParseReadLine always strips trailing whitespace, leaving no room for ambiguities. The other log messages follow common punctuation rules, which makes the beginning of the line equally unambiguous. Before var.c 1.911 from 2021-04-05, variable assignments were logged with the format "%s:%s = %s", without a space after the colon. |
| H A D | deptgt.exp | 1.10 Tue Dec 28 15:49:00 GMT 2021 rillig make: make debug logging a bit more human-friendly The previous log format "ParseReadLine (%d): '%s'" focused on the implementation, it was not immediately obvious to a casual reader that the number in parentheses was the line number. Additionally, having both a colon and quotes in a log message is uncommon. The quotes have been added in parse.c 1.127 from 2007-01-01. The new log format "Parsing line %d: %s" is meant to be easier readable by humans. The quotes are not needed since ParseReadLine always strips trailing whitespace, leaving no room for ambiguities. The other log messages follow common punctuation rules, which makes the beginning of the line equally unambiguous. Before var.c 1.911 from 2021-04-05, variable assignments were logged with the format "%s:%s = %s", without a space after the colon. |
| H A D | directive-export-impl.exp | 1.15 Tue Dec 28 15:49:00 GMT 2021 rillig make: make debug logging a bit more human-friendly The previous log format "ParseReadLine (%d): '%s'" focused on the implementation, it was not immediately obvious to a casual reader that the number in parentheses was the line number. Additionally, having both a colon and quotes in a log message is uncommon. The quotes have been added in parse.c 1.127 from 2007-01-01. The new log format "Parsing line %d: %s" is meant to be easier readable by humans. The quotes are not needed since ParseReadLine always strips trailing whitespace, leaving no room for ambiguities. The other log messages follow common punctuation rules, which makes the beginning of the line equally unambiguous. Before var.c 1.911 from 2021-04-05, variable assignments were logged with the format "%s:%s = %s", without a space after the colon. |
| H A D | suff-main-several.exp | 1.7 Tue Dec 28 15:49:00 GMT 2021 rillig make: make debug logging a bit more human-friendly The previous log format "ParseReadLine (%d): '%s'" focused on the implementation, it was not immediately obvious to a casual reader that the number in parentheses was the line number. Additionally, having both a colon and quotes in a log message is uncommon. The quotes have been added in parse.c 1.127 from 2007-01-01. The new log format "Parsing line %d: %s" is meant to be easier readable by humans. The quotes are not needed since ParseReadLine always strips trailing whitespace, leaving no room for ambiguities. The other log messages follow common punctuation rules, which makes the beginning of the line equally unambiguous. Before var.c 1.911 from 2021-04-05, variable assignments were logged with the format "%s:%s = %s", without a space after the colon. |
| H A D | varname-dot-shell.exp | 1.13 Tue Dec 28 15:49:00 GMT 2021 rillig make: make debug logging a bit more human-friendly The previous log format "ParseReadLine (%d): '%s'" focused on the implementation, it was not immediately obvious to a casual reader that the number in parentheses was the line number. Additionally, having both a colon and quotes in a log message is uncommon. The quotes have been added in parse.c 1.127 from 2007-01-01. The new log format "Parsing line %d: %s" is meant to be easier readable by humans. The quotes are not needed since ParseReadLine always strips trailing whitespace, leaving no room for ambiguities. The other log messages follow common punctuation rules, which makes the beginning of the line equally unambiguous. Before var.c 1.911 from 2021-04-05, variable assignments were logged with the format "%s:%s = %s", without a space after the colon. |
| H A D | varmod-loop.exp | 1.14 Tue Dec 28 15:49:00 GMT 2021 rillig make: make debug logging a bit more human-friendly The previous log format "ParseReadLine (%d): '%s'" focused on the implementation, it was not immediately obvious to a casual reader that the number in parentheses was the line number. Additionally, having both a colon and quotes in a log message is uncommon. The quotes have been added in parse.c 1.127 from 2007-01-01. The new log format "Parsing line %d: %s" is meant to be easier readable by humans. The quotes are not needed since ParseReadLine always strips trailing whitespace, leaving no room for ambiguities. The other log messages follow common punctuation rules, which makes the beginning of the line equally unambiguous. Before var.c 1.911 from 2021-04-05, variable assignments were logged with the format "%s:%s = %s", without a space after the colon. |
| H A D | var-eval-short.exp | 1.18 Tue Dec 28 15:49:00 GMT 2021 rillig make: make debug logging a bit more human-friendly The previous log format "ParseReadLine (%d): '%s'" focused on the implementation, it was not immediately obvious to a casual reader that the number in parentheses was the line number. Additionally, having both a colon and quotes in a log message is uncommon. The quotes have been added in parse.c 1.127 from 2007-01-01. The new log format "Parsing line %d: %s" is meant to be easier readable by humans. The quotes are not needed since ParseReadLine always strips trailing whitespace, leaving no room for ambiguities. The other log messages follow common punctuation rules, which makes the beginning of the line equally unambiguous. Before var.c 1.911 from 2021-04-05, variable assignments were logged with the format "%s:%s = %s", without a space after the colon. |
| H A D | varmod-indirect.exp | 1.20 Tue Dec 28 15:49:00 GMT 2021 rillig make: make debug logging a bit more human-friendly The previous log format "ParseReadLine (%d): '%s'" focused on the implementation, it was not immediately obvious to a casual reader that the number in parentheses was the line number. Additionally, having both a colon and quotes in a log message is uncommon. The quotes have been added in parse.c 1.127 from 2007-01-01. The new log format "Parsing line %d: %s" is meant to be easier readable by humans. The quotes are not needed since ParseReadLine always strips trailing whitespace, leaving no room for ambiguities. The other log messages follow common punctuation rules, which makes the beginning of the line equally unambiguous. Before var.c 1.911 from 2021-04-05, variable assignments were logged with the format "%s:%s = %s", without a space after the colon. |
| /src/sys/dev/pci/ | ||
| H A D | pcidevs.h | 1.911 Tue Oct 30 00:39:48 GMT 2007 xtraeme regen |
| H A D | pcidevs_data.h | 1.911 Tue Oct 30 20:44:31 GMT 2007 xtraeme regen |
| H A D | pcidevs | 1.911 Tue Oct 30 20:44:12 GMT 2007 xtraeme Add Intel IOP332 A/B Segments. |
| /src/distrib/sets/lists/base/ | ||
| H A D | shl.mi | 1.911 Fri Feb 19 17:06:26 GMT 2021 christos bump bind libraries |
| H A D | mi | 1.911 Sat Jan 01 00:49:49 GMT 2011 haad Add /var/lock directory to base set it's used by LVM and other tools. Change group owner to operator to enable LVM locking for him. |
| /src/doc/ | ||
| H A D | 3RDPARTY | 1.911 Fri Feb 17 11:15:59 GMT 2012 tron Postfix was updated to version 2.8.8. |
| /src/usr.bin/make/ | ||
| H A D | parse.c | 1.591 Tue Dec 28 15:48:59 GMT 2021 rillig make: make debug logging a bit more human-friendly The previous log format "ParseReadLine (%d): '%s'" focused on the implementation, it was not immediately obvious to a casual reader that the number in parentheses was the line number. Additionally, having both a colon and quotes in a log message is uncommon. The quotes have been added in parse.c 1.127 from 2007-01-01. The new log format "Parsing line %d: %s" is meant to be easier readable by humans. The quotes are not needed since ParseReadLine always strips trailing whitespace, leaving no room for ambiguities. The other log messages follow common punctuation rules, which makes the beginning of the line equally unambiguous. Before var.c 1.911 from 2021-04-05, variable assignments were logged with the format "%s:%s = %s", without a space after the colon. |
| H A D | var.c | 1.911 Mon Apr 05 13:35:41 GMT 2021 rillig make: in debug log, add space between scope and variable name Without this space, the debug log looked more like line noise, even though the only punctuation was a single innocent ':'. From a make user's perspective, the variable name is a word of its own and should not be visually glued to its namespace. |
| /src/sys/arch/i386/conf/ | ||
| H A D | GENERIC | 1.911 Tue Oct 07 09:30:04 GMT 2008 rmind Add a note that SysV IPC parameters could be changed dynamically. |
| /src/distrib/sets/lists/man/ | ||
| H A D | mi | 1.911 Sun Jul 23 00:01:25 GMT 2006 bouyer Add a /dev/amr* control file for amr(4) devices, which allows sending raw commands to the controller. Add a amrctl(8) control tool, which for now only allows to get status from the adapter (status of adapter, logical volumes and and individual drives). From FreeBSD, with some adjustements by Andrew Doran and me. |
| /src/distrib/sets/lists/tests/ | ||
| H A D | mi | 1.911 Fri Aug 28 03:51:06 GMT 2020 rillig make(1): add tests for the special .INCLUDES and .LIBS variables |
| /src/share/mk/ | ||
| H A D | bsd.own.mk | 1.911 Sat Mar 26 10:35:14 GMT 2016 martin Switch playstation2 over to gcc 5.3, binutils 2.26 and gdb 7.10 |
| /src/sys/conf/ | ||
| H A D | files | 1.911 Thu Jul 31 05:38:04 GMT 2008 simonb Merge the simonb-wapbl branch. From the original branch commit: Add Wasabi System's WAPBL (Write Ahead Physical Block Logging) journaling code. Originally written by Darrin B. Jewell while at Wasabi and updated to -current by Antti Kantee, Andy Doran, Greg Oster and Simon Burge. OK'd by core@, releng@. |
| /src/distrib/sets/lists/comp/ | ||
| H A D | mi | 1.911 Mon Aug 21 04:13:28 GMT 2006 thorpej Several changes to proplib: - Arrays can now be externalized and internalized in the same way dictionaries can. - Add new "externalize to file" and "internalize from file" functions to make reading a property list from a file and writing a property list to a file more convenient. - Many assertions in the object implementations are gone. Instead, calling an accessor for one object type with a different object type as an argument will return a suitable "invalid" value. - prop_object_type() now returns a new PROP_TYPE_UNKNOWN value if called with a NULL object. - Externalized property lists now contain a reference to the Apple XML plist DTD. - Add a new prop_ingest(3) facility, which provides a convenient way to translate a dictionary into an arbitrary binary representation. |
Completed in 1247 milliseconds