Date: Fri, 17 Jun 2005 12:08:37 +0300 From: Giorgos Keramidas <keramida@freebsd.org> To: Hideyuki KURASHINA <rushani@bl.mmtr.or.jp> Cc: doc-committers@freebsd.org, cvs-doc@freebsd.org, cvs-all@freebsd.org Subject: Re: cvs commit: doc/ja_JP.eucJP/books/handbook/desktop chapter.sgml Message-ID: <20050617090837.GC791@flame.pc> In-Reply-To: <20050616.054643.55424432.rushani@bl.mmtr.or.jp> References: <200506152034.j5FKYqrZ030874@repoman.freebsd.org> <20050616.054643.55424432.rushani@bl.mmtr.or.jp>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2005-06-16 05:46, Hideyuki KURASHINA wrote: >>>> On Wed, 15 Jun 2005 20:34:52 +0000 (UTC), >>>> Hideyuki KURASHINA <rushani@FreeBSD.org> said: >> rushani 2005-06-15 20:34:52 UTC >> >> FreeBSD doc repository >> >> Modified files: >> ja_JP.eucJP/books/handbook/desktop chapter.sgml >> Log: > > (snip'ed) > > Apologies... > > Sorry, I don't use ``cvs commit -F'' for the next time... Actually, please do. Typing the log message in an offline file and then using: % cvs ci -F logmsg file [...] tends to lock the repository files for the minimal amount of time necessary to do the commit operation. On the other hand, using: % cvs ci and then sitting in an editor (with parts of the repository locked) usually ends up in quite a few problems: - Quickly typed log messages that are a mess, or - Trouble by failing connections that leave stale CVS locks around I've been bitten by both, quite a few times; thankfully, not in the central FreeBSD repository, but other CVS trees. So, please, you are welcome to use cvs commit -F logfile :) - Giorgos
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050617090837.GC791>