From: Francesco Potorti` <pot@gnu.org>
Cc: "Kim F. Storm" <storm@cua.dk>,
system-hackers@gnu.org, cvs-hackers@gnu.org,
savannah-hackers@gnu.org, emacs-devel@gnu.org,
Mathieu Roy <yeupou@gnu.org>
Subject: Re: [Savannah-hackers] Re: emacs/lisp/ChangeLog CVS lock
Date: Fri, 12 Jul 2002 10:23:53 +0200 [thread overview]
Message-ID: <E17SviT-0003Hl-00@pot.cnuce.cnr.it> (raw)
In-Reply-To: <buohej5u2rn.fsf@mcspd15.ucom.lsi.nec.co.jp> (miles@lsi.nec.co.jp)
> MAILTO=cvs-hackers@gnu.org
> */5 * * * * find /cvsroot -name '#cvs.[trw]fl.*' -o -name '#cvs.lock' \
> -mmin +20 -exec rm --force --verbose {} \;
Is `#cvs.lock' a per-file lock, a per-directory lock, or a per-session lock?
As I said, I am *not* a cvs expert. I just read the cvs man page and
extracted all the names of lock files from the FILES section, then put
them together in a find command. Sorry, I don't know more offhand.
next prev parent reply other threads:[~2002-07-12 8:23 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-10 11:22 emacs/lisp/ChangeLog CVS lock Simon Josefsson
2002-07-10 11:51 ` Juanma Barranquero
2002-07-11 7:00 ` Francesco Potorti`
2002-07-11 9:42 ` Kim F. Storm
2002-07-11 11:44 ` [Savannah-hackers] " Mathieu Roy
2002-07-11 12:00 ` Andreas Schwab
2002-07-11 12:15 ` Mathieu Roy
2002-07-11 12:39 ` Andreas Schwab
2002-07-11 14:40 ` Jeff Bailey
2002-07-11 15:41 ` Andreas Schwab
2002-07-11 12:11 ` Francesco Potorti`
2002-07-11 12:16 ` Mathieu Roy
2002-07-12 1:57 ` Miles Bader
2002-07-12 6:36 ` Mathieu Roy
2002-07-12 6:58 ` Miles Bader
2002-07-12 21:53 ` Mathieu Roy
2002-07-12 23:31 ` Kim F. Storm
2002-07-12 8:23 ` Francesco Potorti` [this message]
2002-07-12 2:32 ` GNU Kerberos breakage (was Re: emacs/lisp/ChangeLog CVS lock) Ken Raeburn
2002-07-12 2:55 ` Miles Bader
2002-07-12 3:03 ` Jeff Bailey
2002-07-12 6:00 ` Ken Raeburn
2002-07-12 6:39 ` Joel N. Weber II
2002-07-12 21:17 ` Jeff Bailey
2002-07-14 19:11 ` Ken Raeburn
2002-08-28 15:24 ` emacs/lisp/ChangeLog CVS lock Simon Josefsson
2002-08-29 12:23 ` Simon Josefsson
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E17SviT-0003Hl-00@pot.cnuce.cnr.it \
--to=pot@gnu.org \
--cc=cvs-hackers@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=savannah-hackers@gnu.org \
--cc=storm@cua.dk \
--cc=system-hackers@gnu.org \
--cc=yeupou@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).