[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

local vs client/server for 'cvs status ./.' command

From: Mark D. Baushke
Subject: local vs client/server for 'cvs status ./.' command
Date: Mon, 10 Mar 2003 17:01:45 -0800

Hi Folks,

The cvs server seems to get confused when a "Directory ./.\n" element is
passed across the wire. This can happen when a user specifies './.' (or
././. etc) on the command line.

The same problem does not arise when a local repository is used.

So, the question arises as to the 'best' way to fix this problem to give
the user the expected output.

 -> have the client canonicalize the directory before sending it as an
    Argument to the server.

 -> have the serve_directory function canonicalize the directory by
    trimming any trailing "/." strings.

 -> declare the input an error and tell the user not to do confusing
    things like this.

 -> something else.


        -- Mark

% mkdir /tmp/cvs-sanity
% cvs -d :fork:/tmp/cvs-sanity/cvsroot init
% cd /tmp/cvs-sanity
% cvs -d :fork:/tmp/cvs-sanity/cvsroot checkout CVSROOT
% cvs -d :fork:/tmp/cvs-sanity/cvsroot status ././verifymsg
cvs server: ././verifymsg is no longer in the repository
File: verifymsg         Status: Entry Invalid

   Working revision:    1.1
   Repository revision: No revision control file
   Sticky Tag:          (none)
   Sticky Date:         (none)
   Sticky Options:      (none)

% cvs -d /tmp/cvs-sanity/cvsroot status ././verifymsg
File: verifymsg         Status: Up-to-date

   Working revision:    1.1     Tue Mar 11 00:57:40 2003
   Repository revision: 1.1     /tmp/cvs-sanity/cvsroot/CVSROOT/verifymsg,v
   Sticky Tag:          (none)
   Sticky Date:         (none)
   Sticky Options:      (none)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]