summaryrefslogtreecommitdiffstats
path: root/usr.bin/cvs/fatal.c (follow)
Commit message (Collapse)AuthorAgeFilesLines
* show any signal we might have received that killed our cvs process.joris2008-06-121-4/+8
| | | | ok tobias@
* Stick at GNU cvs behaviour with Root directive handling: it does not needtobias2007-09-021-2/+3
| | | | | | | to be sent first, can occure multiple times (although this is ignored) but should be supplied before Directory. OK joris@
* I've been running with an abort upon fatal loop, and I think I'veray2007-05-291-3/+3
| | | | | | | | | mostly gotten rid of them. It would be nice to know if there is a fatal loop instead of dying quietly, so call errx instead of exit(1). errx does not call fatal so it should be fine. OK niallo@
* It is too complicated to tell a client that an internal failureray2007-05-261-4/+1
| | | | | | | happened in fatal(). If that behavior is desired, please tell the client before calling fatal(). OK niallo@
* fatal() should never be called twice; if it happens, exit immediately,ray2007-05-261-1/+7
| | | | | | it is the only safe thing to do. OK niallo@
* general includes cleanup sweep. ok joris@ niallo@otto2007-02-221-3/+5
|
* first part of opencvs remote, fairly useable on existing treesjoris2006-07-071-1/+5
| | | | | | | | | | | | | | although i advise against using it on real development trees for now. only a few commands work right so far: - commit - diff - status - log - update (partially working) if you feel like testing remote and run into bugs feel free to contact me, and please include a full trace (-t).
* commit the new opencvs code, i have been hacking onjoris2006-05-271-1/+4
| | | | | | | | | | | | this for the past 2 weeks now and it should go in at the start of the hackathon so others can help out. this code is a lot safer, smarter, faster and best of all it is actually doing what it is suppose to do! basic checkout, update, status, diff and commit are working in local mode only. there is no support for any remote setups now.
* - make fatal() exit with code 1 instead of 255. makes us more compatibleniallo2006-01-301-2/+2
| | | | | | with gnu on errors. ok xsa@
* #include's cleanup; ok joris@ niallo@.xsa2006-01-021-3/+2
|
* pass LP_ABORT to cvs_vlog() instead of LP_ERR.joris2005-12-301-2/+2
|
* we should be calling cvs_vlog(); to at least get some decent output;joris2005-12-241-2/+3
|
* add missing $OpenBSD$xsa2005-12-131-0/+1
|
* switch to xmalloc stuff, me and xsa@ agreed on this a longjoris2005-12-101-0/+41
time ago, but we were being held back by jfb. too bad for him. next step is to use fatal() through out the code for unrecoverable errors instead of trying to be all nice and fluffy and reach main() again. ok niallo@ and xsa@
Copyright © 1996 – 2023 Jason A. Donenfeld. All Rights Reverse Engineered.