From: Simon Josefsson <jas@extundo.com>
Cc: emacs-devel@gnu.org
Subject: Re: emacs/lisp/ChangeLog CVS lock
Date: Wed, 28 Aug 2002 17:24:39 +0200 [thread overview]
Message-ID: <ilusn0zvweg.fsf@latte.josefsson.org> (raw)
In-Reply-To: <iluu1n7g750.fsf@latte.josefsson.org> (Simon Josefsson's message of "Wed, 10 Jul 2002 13:22:03 +0200")
Ok, so it happened again. Could someone please remove the lock?
Same file and same CVS version used as in the report below...
I'm terribly sorry for the trouble, but I think the frequency of this
suggest there is a real bug somewhere. I use CVS extensively and this
is the only one server and only one file I have had these troubles
with. Note that I can commit to other files in the Emacs CVS without
problems. Any ideas?
This is on Debian Sid.
Simon Josefsson <jas@extundo.com> writes:
> (Copied to both cvs-hackers and savannah-hackers since I'm not sure
> which one removed the lock yesterday.)
>
> It seems to have happened again, my "cvs commit ChangeLog" has now
> been hanging for 5 minutes or so, I'm not pressing C-c this time but
> leave it running.
>
> Am I causing this somehow? Again, sorry for the trouble.
>
> bash-2.05a$ cvs --version
>
> Concurrent Versions System (CVS) 1.11.2 (client/server)
>
> Copyright (c) 1989-2001 Brian Berliner, david d `zoo' zuhn,
> Jeff Polk, and other authors
>
> CVS may be copied only under the terms of the GNU General Public License,
> a copy of which can be found with the CVS distribution kit.
>
> Specify the --help option for further information about CVS
> bash-2.05a$ cvs commit ChangeLog
>
> Log message unchanged or not specified
> a)bort, c)ontinue, e)dit, !)reuse this message unchanged for remaining dirs
> Action: (continue) c
>
> <HANGING>
>
>
> _______________________________________________
> Emacs-devel mailing list
> Emacs-devel@gnu.org
> http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-08-28 15:24 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`
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 ` Simon Josefsson [this message]
2002-08-29 12:23 ` emacs/lisp/ChangeLog CVS lock 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=ilusn0zvweg.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--cc=emacs-devel@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).