Date: Sat, 19 Aug 1995 19:34:48 +0800 (WST) From: Peter Wemm <peter@haywire.dialix.com> To: Satoshi Asami <asami@cs.berkeley.edu> Cc: rgrimes@gndrsh.aac.dev.com, CVS-commiters@freefall.FreeBSD.org, cvs-ports@freefall.FreeBSD.org Subject: Re: cvs commit: ports/utils Makefile Message-ID: <Pine.SV4.3.91.950819192125.4730C-100000@haywire.DIALix.COM> In-Reply-To: <199508191045.DAA07591@silvia.HIP.Berkeley.EDU>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 19 Aug 1995, Satoshi Asami wrote: > * Bad thing is the first one goes in the rlog of the first file, and > * the second one goes to the second file :-(. No big deal, a cvs diff > * clear shows who ``these kids'' are. > > Oh, I know that, that's why I said "mail message", just wanted to save > people reading this from having to do cvs diff. :) > > By the way, is there a way to stop the commit in the middle, _after_ > I've saved at least one of the commit messages? Last time I suspended > emacs and killed cvs, the first half was already done and no mail went > out.... Hmm.. If you quit the editor part way through without saving changes, it'll ask if you want to either use the last message, or abort. If you choose abort, it'll cleanly exit, but it will not send an email for the first part of the commit.. BTW: suspending emacs and killing cvs is a 'bad thing', because it can leave a lock on the directory in ~ncvs.. (here, you can have this morning's conical hat back again.. :-). What happens then, is the "cvs updates" that are run from cron will block indefinately, and then Rod has to do a find looking for the locks. There's a patch for cvs-1.5 that will stop this from happening, BTW.. Paul Eggert (the RCS maintainer) submitted it just before 1.5 was released, and it was "too major" to risk at the last minute. > Satoshi (well I guess not) BTW: What I'd suggest might be an option in real emergencies with a commit running and potentially causing mass destruction, would be to hit ^Z and scream for help.. Then, Rod or Myself could find out which is the safest way out.. Cheers, -Peter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.SV4.3.91.950819192125.4730C-100000>