Searched hist:1.127 (Results 1 - 25 of 594) 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. |
| /src/sys/ufs/lfs/ | ||
| H A D | ulfs_quota1.c | 1.10 Mon Jun 20 00:00:47 GMT 2016 dholland More already-merged or equivalent changes: ufs_dirhash.c 1.36 corresponds to ulfs_dirhash.c 1.8 ufs_extattr.c 1.43 corresponds to ulfs_extattr.c 1.7 ufs_lookup.c 1.126 does not apply to lfs ufs_lookup.c 1.127 we already have ufs_lookup.c 1.128 does not apply to lfs ufs_lookup.c 1.129 corresponds to ulfs_lookup.c 1.19 ufs_quota1.c 1.19 corresponds to ulfs_quota1.c 1.7 ufs_quota1.c 1.20 corresponds to ulfs_quota1.c 1.8 ufs_quota2.c 1.36 we have equivalent changes for ufs_rename.c 1.9 corresponds to lfs_rename.c 1.5 ufs_rename.c 1.10 corresponds to lfs_rename.c 1.6 ufs_vnops.c 1.219 corresponds to lfs_vnops.c 1.260 and ulfs_vnops.c 1.19 ufs_vnops.c 1.220 corresponds to lfs_vnops.c 1.261 and ulfs_vnops.c 1.20 ufs_vnops.c 1.221 was superseded by later changes ufs_vnops.c 1.222 got fixed independently in lfs |
| H A D | ulfs_dirhash.c | 1.16 Mon Jun 20 00:00:47 GMT 2016 dholland More already-merged or equivalent changes: ufs_dirhash.c 1.36 corresponds to ulfs_dirhash.c 1.8 ufs_extattr.c 1.43 corresponds to ulfs_extattr.c 1.7 ufs_lookup.c 1.126 does not apply to lfs ufs_lookup.c 1.127 we already have ufs_lookup.c 1.128 does not apply to lfs ufs_lookup.c 1.129 corresponds to ulfs_lookup.c 1.19 ufs_quota1.c 1.19 corresponds to ulfs_quota1.c 1.7 ufs_quota1.c 1.20 corresponds to ulfs_quota1.c 1.8 ufs_quota2.c 1.36 we have equivalent changes for ufs_rename.c 1.9 corresponds to lfs_rename.c 1.5 ufs_rename.c 1.10 corresponds to lfs_rename.c 1.6 ufs_vnops.c 1.219 corresponds to lfs_vnops.c 1.260 and ulfs_vnops.c 1.19 ufs_vnops.c 1.220 corresponds to lfs_vnops.c 1.261 and ulfs_vnops.c 1.20 ufs_vnops.c 1.221 was superseded by later changes ufs_vnops.c 1.222 got fixed independently in lfs |
| H A D | ulfs_extattr.c | 1.9 Mon Jun 20 00:00:47 GMT 2016 dholland More already-merged or equivalent changes: ufs_dirhash.c 1.36 corresponds to ulfs_dirhash.c 1.8 ufs_extattr.c 1.43 corresponds to ulfs_extattr.c 1.7 ufs_lookup.c 1.126 does not apply to lfs ufs_lookup.c 1.127 we already have ufs_lookup.c 1.128 does not apply to lfs ufs_lookup.c 1.129 corresponds to ulfs_lookup.c 1.19 ufs_quota1.c 1.19 corresponds to ulfs_quota1.c 1.7 ufs_quota1.c 1.20 corresponds to ulfs_quota1.c 1.8 ufs_quota2.c 1.36 we have equivalent changes for ufs_rename.c 1.9 corresponds to lfs_rename.c 1.5 ufs_rename.c 1.10 corresponds to lfs_rename.c 1.6 ufs_vnops.c 1.219 corresponds to lfs_vnops.c 1.260 and ulfs_vnops.c 1.19 ufs_vnops.c 1.220 corresponds to lfs_vnops.c 1.261 and ulfs_vnops.c 1.20 ufs_vnops.c 1.221 was superseded by later changes ufs_vnops.c 1.222 got fixed independently in lfs |
| H A D | lfs_rename.c | 1.18 Mon Jun 20 00:00:47 GMT 2016 dholland More already-merged or equivalent changes: ufs_dirhash.c 1.36 corresponds to ulfs_dirhash.c 1.8 ufs_extattr.c 1.43 corresponds to ulfs_extattr.c 1.7 ufs_lookup.c 1.126 does not apply to lfs ufs_lookup.c 1.127 we already have ufs_lookup.c 1.128 does not apply to lfs ufs_lookup.c 1.129 corresponds to ulfs_lookup.c 1.19 ufs_quota1.c 1.19 corresponds to ulfs_quota1.c 1.7 ufs_quota1.c 1.20 corresponds to ulfs_quota1.c 1.8 ufs_quota2.c 1.36 we have equivalent changes for ufs_rename.c 1.9 corresponds to lfs_rename.c 1.5 ufs_rename.c 1.10 corresponds to lfs_rename.c 1.6 ufs_vnops.c 1.219 corresponds to lfs_vnops.c 1.260 and ulfs_vnops.c 1.19 ufs_vnops.c 1.220 corresponds to lfs_vnops.c 1.261 and ulfs_vnops.c 1.20 ufs_vnops.c 1.221 was superseded by later changes ufs_vnops.c 1.222 got fixed independently in lfs |
| /src/sys/dev/mii/ | ||
| H A D | miidevs.h | 1.127 Fri Aug 14 01:26:38 GMT 2015 knakahara branches: 1.127.2; 1.127.4; regen 1.127 Fri Aug 14 01:26:38 GMT 2015 knakahara branches: 1.127.2; 1.127.4; regen 1.127 Fri Aug 14 01:26:38 GMT 2015 knakahara branches: 1.127.2; 1.127.4; regen |
| /src/sys/dev/pci/ | ||
| H A D | auich.c | 1.127 Sun May 04 15:58:51 GMT 2008 xtraeme branches: 1.127.6; 1.127.8; 1.127.10; 1.127.14; device_t/softc split and other related cosmetic changes. 1.127 Sun May 04 15:58:51 GMT 2008 xtraeme branches: 1.127.6; 1.127.8; 1.127.10; 1.127.14; device_t/softc split and other related cosmetic changes. 1.127 Sun May 04 15:58:51 GMT 2008 xtraeme branches: 1.127.6; 1.127.8; 1.127.10; 1.127.14; device_t/softc split and other related cosmetic changes. 1.127 Sun May 04 15:58:51 GMT 2008 xtraeme branches: 1.127.6; 1.127.8; 1.127.10; 1.127.14; device_t/softc split and other related cosmetic changes. 1.127 Sun May 04 15:58:51 GMT 2008 xtraeme branches: 1.127.6; 1.127.8; 1.127.10; 1.127.14; device_t/softc split and other related cosmetic changes. |
| H A D | pccbb.c | 1.127 Sun Dec 18 11:04:00 GMT 2005 sekiya branches: 1.127.4; 1.127.6; 1.127.8; 1.127.10; 1.127.12; Use aprint_debug() instead of printf() for obvious debug statement. 1.127 Sun Dec 18 11:04:00 GMT 2005 sekiya branches: 1.127.4; 1.127.6; 1.127.8; 1.127.10; 1.127.12; Use aprint_debug() instead of printf() for obvious debug statement. 1.127 Sun Dec 18 11:04:00 GMT 2005 sekiya branches: 1.127.4; 1.127.6; 1.127.8; 1.127.10; 1.127.12; Use aprint_debug() instead of printf() for obvious debug statement. 1.127 Sun Dec 18 11:04:00 GMT 2005 sekiya branches: 1.127.4; 1.127.6; 1.127.8; 1.127.10; 1.127.12; Use aprint_debug() instead of printf() for obvious debug statement. 1.127 Sun Dec 18 11:04:00 GMT 2005 sekiya branches: 1.127.4; 1.127.6; 1.127.8; 1.127.10; 1.127.12; Use aprint_debug() instead of printf() for obvious debug statement. 1.127 Sun Dec 18 11:04:00 GMT 2005 sekiya branches: 1.127.4; 1.127.6; 1.127.8; 1.127.10; 1.127.12; Use aprint_debug() instead of printf() for obvious debug statement. |
| /src/sys/compat/linux/arch/i386/ | ||
| H A D | linux_syscall.h | 1.127 Sat Jun 29 13:46:32 GMT 2024 christos branches: 1.127.2; regen 1.127 Sat Jun 29 13:46:32 GMT 2024 christos branches: 1.127.2; regen 1.127 Sat Jun 29 13:46:32 GMT 2024 christos branches: 1.127.2; regen 1.127 Sat Jun 29 13:46:32 GMT 2024 christos branches: 1.127.2; regen |
| H A D | linux_sysent.c | 1.127 Sat Jun 29 13:46:32 GMT 2024 christos branches: 1.127.2; regen 1.127 Sat Jun 29 13:46:32 GMT 2024 christos branches: 1.127.2; regen |
| H A D | linux_syscallargs.h | 1.127 Sat Jun 29 13:46:32 GMT 2024 christos branches: 1.127.2; regen 1.127 Sat Jun 29 13:46:32 GMT 2024 christos branches: 1.127.2; regen |
| /src/sys/kern/ | ||
| H A D | sys_process.c | 1.127 Sat Jul 21 19:21:53 GMT 2007 ad branches: 1.127.4; 1.127.6; 1.127.8; Merge unobtrusive locking changes from the vmlocking branch. 1.127 Sat Jul 21 19:21:53 GMT 2007 ad branches: 1.127.4; 1.127.6; 1.127.8; Merge unobtrusive locking changes from the vmlocking branch. 1.127 Sat Jul 21 19:21:53 GMT 2007 ad branches: 1.127.4; 1.127.6; 1.127.8; Merge unobtrusive locking changes from the vmlocking branch. 1.127 Sat Jul 21 19:21:53 GMT 2007 ad branches: 1.127.4; 1.127.6; 1.127.8; Merge unobtrusive locking changes from the vmlocking branch. |
| H A D | sys_generic.c | 1.127 Wed Jul 27 14:35:34 GMT 2011 uebayasi branches: 1.127.2; 1.127.6; These don't need uvm/uvm_extern.h. 1.127 Wed Jul 27 14:35:34 GMT 2011 uebayasi branches: 1.127.2; 1.127.6; These don't need uvm/uvm_extern.h. 1.127 Wed Jul 27 14:35:34 GMT 2011 uebayasi branches: 1.127.2; 1.127.6; These don't need uvm/uvm_extern.h. |
| /src/sys/dev/ic/ | ||
| H A D | z8530tty.c | 1.127 Fri May 22 03:51:30 GMT 2009 mrg branches: 1.127.4; 1.127.6; add two new functions for z8530tty: zs_chan_lock() and zs_chan_unlock(), and use them instead of various spl's in the zs.c's. reviewed by ad and martin. 1.127 Fri May 22 03:51:30 GMT 2009 mrg branches: 1.127.4; 1.127.6; add two new functions for z8530tty: zs_chan_lock() and zs_chan_unlock(), and use them instead of various spl's in the zs.c's. reviewed by ad and martin. 1.127 Fri May 22 03:51:30 GMT 2009 mrg branches: 1.127.4; 1.127.6; add two new functions for z8530tty: zs_chan_lock() and zs_chan_unlock(), and use them instead of various spl's in the zs.c's. reviewed by ad and martin. |
| /src/sys/arch/mvme68k/mvme68k/ | ||
| H A D | machdep.c | 1.127 Sat Jan 12 09:54:29 GMT 2008 tsutsui branches: 1.127.6; 1.127.10; 1.127.12; 1.127.14; Misc cleanup: - KNF, ANSIfy, remove __P() - use __func__ to print function names - use __arraycount() - include "ioconf.h" for struct cfdriver - u_intNN_t -> uintNN_t - wrap long lines etc. 1.127 Sat Jan 12 09:54:29 GMT 2008 tsutsui branches: 1.127.6; 1.127.10; 1.127.12; 1.127.14; Misc cleanup: - KNF, ANSIfy, remove __P() - use __func__ to print function names - use __arraycount() - include "ioconf.h" for struct cfdriver - u_intNN_t -> uintNN_t - wrap long lines etc. 1.127 Sat Jan 12 09:54:29 GMT 2008 tsutsui branches: 1.127.6; 1.127.10; 1.127.12; 1.127.14; Misc cleanup: - KNF, ANSIfy, remove __P() - use __func__ to print function names - use __arraycount() - include "ioconf.h" for struct cfdriver - u_intNN_t -> uintNN_t - wrap long lines etc. 1.127 Sat Jan 12 09:54:29 GMT 2008 tsutsui branches: 1.127.6; 1.127.10; 1.127.12; 1.127.14; Misc cleanup: - KNF, ANSIfy, remove __P() - use __func__ to print function names - use __arraycount() - include "ioconf.h" for struct cfdriver - u_intNN_t -> uintNN_t - wrap long lines etc. 1.127 Sat Jan 12 09:54:29 GMT 2008 tsutsui branches: 1.127.6; 1.127.10; 1.127.12; 1.127.14; Misc cleanup: - KNF, ANSIfy, remove __P() - use __func__ to print function names - use __arraycount() - include "ioconf.h" for struct cfdriver - u_intNN_t -> uintNN_t - wrap long lines etc. |
| /src/sys/arch/sun3/conf/ | ||
| H A D | GENERIC | 1.127 Fri Dec 09 23:34:03 GMT 2005 elad branches: 1.127.2; 1.127.4; Add (commented out) Veriexec options and pseudo-device to GENERIC kernels, and remove the i386 GENERIC_VERIEXEC config. 1.127 Fri Dec 09 23:34:03 GMT 2005 elad branches: 1.127.2; 1.127.4; Add (commented out) Veriexec options and pseudo-device to GENERIC kernels, and remove the i386 GENERIC_VERIEXEC config. 1.127 Fri Dec 09 23:34:03 GMT 2005 elad branches: 1.127.2; 1.127.4; Add (commented out) Veriexec options and pseudo-device to GENERIC kernels, and remove the i386 GENERIC_VERIEXEC config. |
| /src/sys/arch/cobalt/conf/ | ||
| H A D | GENERIC | 1.127 Tue Nov 23 11:13:55 GMT 2010 hannken branches: 1.127.2; 1.127.4; Remove unused count from pseudo-device md. 1.127 Tue Nov 23 11:13:55 GMT 2010 hannken branches: 1.127.2; 1.127.4; Remove unused count from pseudo-device md. 1.127 Tue Nov 23 11:13:55 GMT 2010 hannken branches: 1.127.2; 1.127.4; Remove unused count from pseudo-device md. |
Completed in 130 milliseconds