On 5/1/06, Bill Burdick <bill@xxxxxxxxxxxxxxxxxxx> wrote:
OK, I changed the way I was testing this to match your usage plan and I still got the same results. It works just fine for vanilla CVS; cvs status shows the re revision in the repo and cvs update brings it in.
That's a good start!
Eclipse has the same funky behavior: Compare with latest at the project level shows no differences, but compare with latest on the changed file actually does an update instead of popping up the Eclipse diff viewer.
Hmmm. Eclipse does some weird funky sh*t sometimes. Can you ask it to get you a log? There's an option in Eclipse CVS control settings that will enable logging of cvs commands to the console. Enable it, and then start Eclipse from the commandline, piping stderr and stdout to a logfile. There are also some weird differences depending on how you ask for the update or diff. I hate doing this but I'll have to ask you to tell me exactly how you ask for the diff and for the update. And the platform you are running Eclipse on.
By the way, I had trouble at first accessing the repo with SSH because of permissions on the sqlite db. I'm not totally sure about the implications for multiple users, but maybe just using a common group will work fine?
Yes, a common group is the thing to do. $ chgrp gitusers *sqlite $ chmod g+w *sqlite
I'm really happy with git and git-cvsserver! I'm hoping to be able to standardize on it for our Eclipse work. It seems like it should be
Great to hear that! cheers, martin - : send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html