From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Subject: git-cvsserver won't add new content on update
Date: Thu, 18 Jan 2007 16:16:35 +0000 [thread overview]
Message-ID: <200701181616.38318.andyparkins@gmail.com> (raw)
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 reply other threads:[~2007-01-18 16:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-18 16:16 Andy Parkins [this message]
2007-01-18 16:22 ` git-cvsserver won't add new content on update Shawn O. Pearce
2007-01-18 19:01 ` Martin Langhoff
2007-01-19 9:54 ` Andy Parkins
2007-01-19 7:21 ` Andy Parkins
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=200701181616.38318.andyparkins@gmail.com \
--to=andyparkins@gmail.com \
--cc=git@vger.kernel.org \
/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.
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 NNTP newsgroup(s).