public inbox for
help / color / mirror / Atom feed
Subject: gnats/gnats pr-edit.c internal.c index.c edit. ...
Date: Fri, 09 Nov 2001 14:22:00 -0000	[thread overview]
Message-ID: <> (raw)

CVSROOT:	/cvs/gnats
Module name:	gnats
Changes by:	2001-11-09 14:22:10

Modified files:
	gnats          : pr-edit.c internal.c index.c edit.c 

Log message:
	* pr-edit.c (main): Don't test a "boolean" int value by comparing
	it with 1.
	* index.c (getFirstPR): Always checkPRChain; this decreases the
	chances of writing out stale index data.
	(writeIndex): Check to make sure that index hasn't changed since
	last read, fail with CODE_INVALID_INDEX if it has.  Also generate
	email to admin about the problem. Update indexDesc->mtime after
	writing out new index.
	* cmds.c (GNATS_appnOrRepl): Lock database before editing.
	* pr-edit.c (main): Lock database before --append or --replace in
	non-network mode.
	* edit.c (lock_pr): Quash a race bug in PR locking.  Use basically
	the same code as in lock_gnats.  Report lock time if PR is locked.
	* internal.c (lock_gnats): Changed from using creat(path, 0) to
	atomic open() to eliminate a race in database lock creation.
	* internal.c (punt): Complain to stderr if database is null.
	queue-pr sometimes calls punt() before defining database, and this
	way cron will report the error.
	* (lock): Report pid when locking PR.
	(submit): If there are errors during submission, prompt the user
	to abort or retry.


                 reply	other threads:[~2001-11-09 14:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).