all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: monnier+gnu/emacs@rum.cs.yale.edu
Subject: Re: cvs new-dir Need-Update
Date: Fri, 13 Sep 2002 13:56:59 -0400	[thread overview]
Message-ID: <200209131757.g8DHv0q13875@rum.cs.yale.edu> (raw)
In-Reply-To: 200209131650.g8DGoBI25650@arc.math.ohio-state.edu

> Hi.  Not a bug report, just a question:  When running cvs-examine or
> cvs-mode-revert-buffer, I get always these "new-dirs" which are marked
> "Need-Update", but apparently are obsolete.  I can't update them.  Any
> idea what is going on?

Yes, `cvs -n update' will list these as "new directory" as if `cvs update'
would bring them in.  Problem is, `cvs update' would not bring them in
if you use the `-P' option (which is generally recommended).

In other words, the problem is that `cvs -n update' ignores the `-P'
option.  It's difficult for PCL-CVS to fix it, and I couldn't
find a trivial fix in CVS itself either (although that doesn't say
much because I'm very non-familiar with the code).

One solution is to not use the `-P' option, of course.


	Stefan

PS: In earlier versions of PCL-CVS those messages were not turned into
    `Need-Update' but into mere informational messages.  Such messages
    are less annoying in your case, but `Need-Update' is the right
    thing to do in the case of a true new directory.
    The only solution I can think of is to make it a user-option,
    which is rather a cop-out.

       reply	other threads:[~2002-09-13 17:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200209131650.g8DGoBI25650@arc.math.ohio-state.edu>
2002-09-13 17:56 ` Stefan Monnier [this message]
2002-09-20 19:28   ` cvs new-dir Need-Update Sam Steingold
2002-09-20 20:49     ` Stefan Monnier
2002-09-23 13:29       ` Sam Steingold
2002-09-23 18:06         ` Stefan Monnier

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200209131757.g8DHv0q13875@rum.cs.yale.edu \
    --to=monnier+gnu/emacs@rum.cs.yale.edu \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.