unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Romain Francoise <romain@orebokech.com>
Subject: PCL-CVS: commit updates the wrong lines
Date: Sun, 09 Jan 2005 22:08:59 +0100	[thread overview]
Message-ID: <87zmzi5mz8.fsf@orebokech.com> (raw)

In a CVS mode buffer created using the `cvs-examine' command, if I
commit a file in a subdirectory, after committing the line is not
updated with the version of the new revision.  Instead, a line is added
in the buffer in the top directory listing.

Example: I start with this:

,----
| In directory .:
|               Unknown                 .htaccess
|               Unknown                 404.php
|               Unknown                 rain.jpg
| In directory include:
|               Modified                include/foo.include
`----

I commit the file include/foo.include using `c' on the corresponding
line.  I get:

,----
| In directory .:
|               Unknown                 .htaccess
|               Unknown                 404.php
| committed     Up-To-Date  1.13        foo.include
|               Unknown                 rain.jpg
| In directory include:
|               Modified                include/foo.include
`----

There is no file named foo.include in the top directory. This bug
appeared sometime before October 2004 and now.

-- 
Romain Francoise <romain@orebokech.com> | I'm going out for a little
it's a miracle -- http://orebokech.com/ | drive, and it may be the last
                                        | time you see me alive.

             reply	other threads:[~2005-01-09 21:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-09 21:08 Romain Francoise [this message]
2005-01-09 21:48 ` PCL-CVS: commit updates the wrong lines Stefan Monnier
2005-01-10 15:46   ` Romain Francoise
2005-01-10 17:31     ` Stefan Monnier
2005-01-10 18:41       ` Romain Francoise
2005-01-17  7:28       ` Romain Francoise
2005-01-10 21:16     ` Kevin Rodgers
2005-01-11  7:19       ` Romain Francoise
2005-01-11 12:01       ` Kai Großjohann
2005-01-11 15:12         ` 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

  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=87zmzi5mz8.fsf@orebokech.com \
    --to=romain@orebokech.com \
    /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).