wireguard-openbsd/gnu/usr.bin/cvs/src, branch jd/queueboosts WireGuard implementation for the OpenBSD kernel https://git.zx2c4.com/wireguard-openbsd/atom/gnu/usr.bin/cvs/src?h=jd%2Fqueueboosts 2019-01-10T00:41:40Z Drop dead links to loria.fr and cvshome.org 2019-01-10T00:41:40Z jca jca@openbsd.org 2019-01-10T00:41:40Z urn:sha1:60f2694012ae83f15a500e294160ce3395187650 Pointed out by Matteo Niccoli, ok bluhm@ sthen@ When checking out certain commits by date, cvs got confused. If 2018-10-22T15:18:50Z bluhm bluhm@openbsd.org 2018-10-22T15:18:50Z urn:sha1:58a8d7d93ab48bbce9afa5ee6c3151ec1d213785 there is a vendor branch and a commit on top of it, revision 1.1 was taken instead of the vendor branch. To fix this, compare the vendor date with the current node, and not with the command line date. OK deraadt@ Fix a few, but not all, clang warnings: Use "%s" to print modifiable 2018-07-10T17:45:52Z tb tb@openbsd.org 2018-07-10T17:45:52Z urn:sha1:0971b67f68eabe84e58ba202abe73d50c878d1ac strings, add a couple of braces, ansify a few functions, add and remove a few extra parens. ok jcs When executing ssh, use "--" to indicate end of arguments before the 2017-08-21T16:45:13Z millert millert@openbsd.org 2017-08-21T16:45:13Z urn:sha1:e5dd404e1941d0097f108bb8b6035ff55237b7d1 host name. Adapted from a MirBSD diff by Thorsten Glaser. once cvs's flow-control mechanism has kicked in, stop reading from 2017-04-14T19:39:59Z jcs jcs@openbsd.org 2017-04-14T19:39:59Z urn:sha1:94a18cb59f9d5469fbc350d54305ac5e37bf9043 its local reader until memory usage goes back down below its watermark. during a checkout of a tree with big files (like www) from a fast reader (disk) and a slow writer (net), the amount of data being buffered can back up enough that cvs tries to allocate too many buffers and hits its resource limit, causing death. cvs's flow-control mechanism properly detects this early on, but the message sent to the reader process to stop sending data takes too long to process. take more aggressive action and just stop reading from the reader until the writer has ejected enough data that it can start re-using its already-allocated buffers instead of allocating new ones. ok deraadt Nuke some excess whitespace. 2017-01-20T00:52:49Z krw krw@openbsd.org 2017-01-20T00:52:49Z urn:sha1:5f354d28123b06ef13991e76928d42aa26aae75d admin: add -C option to set a revision's commitid 2016-08-31T13:16:47Z jcs jcs@openbsd.org 2016-08-31T13:16:47Z urn:sha1:f523375bddb75de394e779ed0bdfaf1415148cff this version bails out if the revision has a commitid already ok guenther deraadt tom When the commit message is empty, don't default to c)ontinue 2016-08-16T18:57:10Z tb tb@openbsd.org 2016-08-16T18:57:10Z urn:sha1:34a6a1634ba8ab60308c30328983b965e8ea2976 (committing without log message), but to a)bort. ok jcs, natano; millert and tj agree Pledge cvs(1). 2015-11-17T12:26:47Z jca jca@openbsd.org 2015-11-17T12:26:47Z urn:sha1:f17452b2e1c499632ab87f5fe479a192eb553091 The initial pledge(2) call is broad, we can refine later when we know whether we run in server, pserver client mode or regular client mode. pserver server mode is likely broken, it will either be fixed or removed. With and ok semarie@, "let's proceed." deraadt@ Use crypt_checkpass() instead of strcmp(hash, crypt(password, hash)). 2015-10-30T16:38:55Z millert millert@openbsd.org 2015-10-30T16:38:55Z urn:sha1:62c892f7a4f5aa377ae61215672e1972ce091bc7 Fixes a crash in pserver mode when CVSROOT/passwd contains an old DES password.