unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Stephen Berman <Stephen.Berman@gmx.net>
Cc: emacs-pretest-bug@gnu.org, emacs-devel@gnu.org
Subject: Re: CVS update fails
Date: Tue, 21 Aug 2007 11:43:52 -0400	[thread overview]
Message-ID: <jwvfy2cnbd9.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <876439xa39.fsf@escher.local.home> (Stephen Berman's message of "Tue\, 21 Aug 2007 15\:59\:06 +0200")

>> I just tried to update from CVS and it failed.  I did `M-x
>> cvs-examine' the `M' to mark all files, the `O' and got the messages
>> at the bottom of this post.  When I type `O' the attached single line
>> was inserted into the *cvs* buffer above the file listing:

> I was wrong, the update didn't fail.  The error message led me to
> believe it had failed but the files were in fact updated.  When I ran
> cvs-examine again just now, only a few files needed to be updated and
> the inserted command line was correspondingly brief.  I guess I had
> never run cvs-examine with so many (all?) files needing to be updated
> (new arch tag or what?).  So that is evidently what caused the error
> message:

Rather than mark all the files, you can just use `O' with *no marks* and
with point on the directory you want to update.  Better yet: M-u will update
the toplevel directory on the *cvs* buffer no matter what marks you've
placed.  Updating file-by-file is generally not what you want because it'll
miss the new files/directories.


        Stefan

  reply	other threads:[~2007-08-21 15:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-21  9:53 CVS update fails Stephen Berman
2007-08-21 13:59 ` Stephen Berman
2007-08-21 15:43   ` Stefan Monnier [this message]
2007-08-21 19:12     ` Stephen Berman
2007-08-21 19:31       ` Stefan Monnier
2007-08-21 23:24   ` Richard Stallman
2007-08-22  5:06     ` David Kastrup

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=jwvfy2cnbd9.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=Stephen.Berman@gmx.net \
    --cc=emacs-devel@gnu.org \
    --cc=emacs-pretest-bug@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).