[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #34011] cvs -nq update produces different results
From: |
anonymous |
Subject: |
[bug #34011] cvs -nq update produces different results |
Date: |
Sun, 14 Aug 2011 10:14:46 +0000 |
User-agent: |
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.18) Gecko/20110628 Ubuntu/10.10 (maverick) Firefox/3.6.18 |
URL:
<http://savannah.nongnu.org/bugs/?34011>
Summary: cvs -nq update produces different results
Project: Concurrent Versions System
Submitted by: None
Submitted on: Sun 14 Aug 2011 10:14:45 AM UTC
Category: Bug Report
Severity: 3 - Normal
Item Group: None
Status: None
Privacy: Public
Assigned to: None
Open/Closed: Open
Release:
Discussion Lock: Any
Fixed Release: None
Fixed Feature Release: None
_______________________________________________________
Details:
I have two different repos one remote, on local being rsync'd
remote runs 1.11.12
local runs 1.12.13
When I run:
$ cvs -nq update
I see no files that have been modified
$ cvs -d /var/cvsroot -nq update
I see files in my check-out tree that claim to have been modified
researching I find that in fact the keywords expansions have
in fact mods in the checked-out files, yet the cvs -nq update against the
remote repo does not seem to think the file has been modified.
Is this is a feature or a bug? Something configurable on the server and local
repo that I'm missing?
_______________________________________________________
Reply to this item at:
<http://savannah.nongnu.org/bugs/?34011>
_______________________________________________
Message sent via/by Savannah
http://savannah.nongnu.org/
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [bug #34011] cvs -nq update produces different results,
anonymous <=