From: Andy Parkins <andyparkins@gmail.com>
To: git@vger.kernel.org
Subject: Does git-cvsserver expect all changes to be via CVS?
Date: Fri, 26 Jan 2007 10:37:11 +0000 [thread overview]
Message-ID: <200701261037.13948.andyparkins@gmail.com> (raw)
Hello,
Still messing around with git-cvsserver. It's behaving very strangely, and it
occurred to me that I have not appreciated that there might be a limitation
in it.
Here's what I did.
* CVS user checks out a branch from the repository
* CVS user adds new directory and files
* CVS user checks them in
* git user updates a tracking branch and then working branch to
match latest
* git user makes changes to same files
* git user checks in and pushes the branch
* CVS user runs cvs update
CVS user can't see the changes; forced updates simply checkout the same files
he's just checked in.
I deleted the sqlite table from the git repository and ran the CVS update
again and this time the changed files arrived (but only after a forced
update).
My question then is: does git-cvsserver require that all changes go via
itself? Does it expect you not to use normal git on that repository any
more?
Andy
--
Dr Andy Parkins, M Eng (hons), MIEE
andyparkins@gmail.com
next reply other threads:[~2007-01-26 10:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 10:37 Andy Parkins [this message]
2007-01-26 11:31 ` Does git-cvsserver expect all changes to be via CVS? 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=200701261037.13948.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.