Age | Commit message (Collapse) | Author |
|
|
|
|
|
to set xs->error to XS_BUSY. So it is pointless and misleading to
set xs->error to XS_TIMEOUT, XS_DRIVER_STUFFUP or XS_BUSY just before
returning TRY_AGAIN_LATER.
No functional change.
ok miod@
|
|
uses rfork(RFTHREAD) to create threads, which are presently processes
that are a little more tightly bound together. several new syscalls
added to facilitate a userland thread library.
all conditional on RTHREADS, currently disabled.
ok deraadt
|
|
to set xs->error to XS_BUSY. So it is pointless and misleading to
set xs->error to XS_TIMEOUT, XS_DRIVER_STUFFUP or XS_BUSY just before
returning TRY_AGAIN_LATER.
No functional change.
|
|
- sync checkin_usage() with reality
|
|
|
|
to set xs->error to XS_BUSY. So it is pointless and misleading to
set xs->error to XS_TIMEOUT, XS_DRIVER_STUFFUP or XS_BUSY just before
returning TRY_AGAIN_LATER.
No functional change.
|
|
much, much, much shorter name. It is only used to print cpu revision anyway...
|
|
|
|
They aren't going to be magically supported the next time. Elminates a
long delay at boot time, since TRY_AGAIN_LATER code was recently fixed
to delay a second before retrying and MODE SENSE commands were
reclassified as unsupported.
ok tdeval@ marco@
|
|
with the rest of perl. On OpenBSD PERL_INT_MAX is the same as INT_MAX.
From rse@engelschall.com.
|
|
If you 'vi file.c' and change stuff, then 'make depend && make' you'll
have a file.o file most definately more recent than the latest committed
version of file.c.
Then, if you rm file.c, and cvs update file.c, if 'file.c' is set to the
timestamp of the last committed version, a subsequent 'make' will not
rebuild the .o file.
to fix this we simply use the current timestamp when updating files.
thanks todd@!
|
|
now, when you checkout a tree with gnu cvs, opencvs no longer sees all
the files as modified, and visa versa.
this actually makes gnu cvs and opencvs dance together in working copies.
|
|
it it exists in the CVS admin dir.
- when writing the Entries file write it to Entries.Backup first and
then rename it to Entries when the writing was successfull.
|
|
on all running processors.
Tested aoyama@ and I
|
|
|
|
|
|
|
|
|
|
|
|
From augustss NetBSD
ok dlg@
|
|
|
|
|
|
|
|
now that lint deals with attributes.
|
|
- checkout in local mode (example: /cvs)
- update in local and server mode (example: /cvs and user@host:/cvs)
- import in local and server mode (example: /cvs and user@host:/cvs)
what remains to be done:
- not all options are supported yet, and update cannot pick up newly
added files yet. these things are pending and will be commited
real soon.
- checkout only works locally right now.
- fix rcs parsing code so that we don't fucking hog 100% cpu
on really BIG BIG BIG ass trees.
mainly tested by pedro@ and myself, thanks a lot pedro!
"go for it" niallo@
|
|
either in our tree or in the gcc docs. See regression test 11 for examples
of this. Right now, our cdefs.h actually defines __attribute__(x) to blank
when lint runs. We can change this whenever we choose.
|
|
|
|
ok cloder@
|
|
|
|
no functional change.
|
|
|
|
instead of symbol address. okay drahn@
|
|
found and tested by pedro@ and niallo@
ok niallo@
|
|
|
|
|
|
The -y option tells lint1 to output yacc debug information (if it was
compiled with YYDEBUG=1).
|
|
enums that are mutually exclusive with each other. Makes this file so
much neater.
|
|
Diff from Iruata Souza, thanks.
|
|
found after prodding by deraadt@
|
|
every signal received writes 1 byte to the socketpair. if you are outside
the libevent main loop too long, the socketpair might fill up. that write
would then block, in a signal handler. related to this, yesterdy we changed
the signal handler to not trash errno.
as for the read end, there will be multiple libevent reads off the socketpair
(100 bytes at a time) until the socketpair is empty again
ok provos
|
|
|
|
|
|
If the given value is too small default to 87.5Mhz, if it is
too high default to 108Mhz.
ok mickey@
|
|
|
|
- make it work as expected (e.g. when no lock set at all too)
- add missing word in error message
- minor knf
|
|
|
|
- move up the lock check
- better error message if a specified rev is too low
OK niallo@.
|
|
remains sorted. Tested and OK norby@
|