git/list[1] front-page[2] threads[3] people[4] search[5] about
 

git-cvsserver won't add new content on update

From
APAndy Parkins <andyparkins@gmail.com>
Date
Jan 18, 2007, 16:16 UTC
Message-ID
<200701181616.38318.andyparkins@gmail.com>
Hello,

I am trying to use git-cvsserver to supply CVS access to my git repository. The checkout worked okay, but now, during normal operation, I've made changes and added content. After a cvs update the changed files all seem to have been updated as expected, however the added files are not being added. However, CVS is reporting that the file is added; but it never appears.

some/sub/directory$ cvs update A some/sub/directory/file.c

After the above the file is not created. Repeated cvs update calls result in the same output everytime. I've tried it from the root of the tree (in case it was a path issue) and that fails in the same way. I've tried specifying the path explicitly and that doesn't help either. cvs status reports that the file is "Status: Needs Checkout".

A new cvs checkout in a different directory does get the new file, so this is a problem with updates only.

I'm not familiar with CVS so it could easily be that I've not understood; however the CVS tutorials say that this should be giving "U" output instead of "A" output.

So: is this a bug, or is it that (as usual) I've not done something terribly 
simple.
Andy
-- 
Dr Andy Parkins, M Eng (hons), MIEE
andyparkins@gmail.com
Next: Shawn O. Pearce
Message 1 of 5 in “git-cvsserver won't add new content on update”
  1. Andy ParkinsJan 18, 2007
  2. Shawn O. PearceJan 18, 2007
  3. Martin LanghoffJan 18, 2007
  4. Andy ParkinsJan 19, 2007
  5. Andy ParkinsJan 19, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.