I'm trying to get sources from
:pserver:anonymous#dev.eclipse.org:/cvsroot/eclipse
using git csvserver. I've just read Best practices for using git with CVS and tried different commands including
git cvsimport -p xCW2quwz6OlRE -d anonymous#dev.eclipse.org:/cvsroot/eclipse /cvsroot/eclipse
but I don't get past the password prompt (the password in the above line is probably pure nonsense, but it doesn't matter). According to the eclipse CVS_Howto the password should be empty (I've tried leaving the -p option out as well).
cvs -d :pserver:anonymous#dev.eclipse.org:/cvsroot/eclipse login
git cvsimport -v -d :pserver:anonymous#dev.eclipse.org:/cvsroot/eclipse -C eclipse -r cvs -k <module_name>
Choose module_name from http://dev.eclipse.org/viewcvs/viewvc.cgi/ e.g platform
Cheers,
Max
As mentioned in the comments, there are mirrors of most of the CVS projects in a git mirror site.
There are also a number of eclipse projects in the process of moving from CVS to Git. See http://git.eclipse.org/ for a list of projects moving. SWT is in the process of moving now.
Related
I am working on a Debian server, where I installed bugzilla. According to the suggestions in the gitzilla-installation guidelines, I would like to integrate Gitzilla to a project on github.com, using the github.com-project as my central repo. Therefore, I am not quite sure, where to do the following steps:
Switch to the hooks directory (/path/to/repository/.git/hooks) and delete the post-receive and update hooks.
Link (or copy) the gitzilla provided hooks:
ln -s $(which gitzilla-post-receive) post-receive
ln -s $(which gitzilla-update) update
Moreover, I tested to choose my github.com-URL to integrate in the /etc/gitzillarc, but without success. PyBugz is installed, and I defined the link to bugzilla, the user_name and PW of the bugzilla-admin.
Best,
H.M.
https://github.com/your_repository.git/.git/hooks will be the path where you should execute the steps.
In case you have a bare repository, then https://github.com/your_repository.git/hooks would be the path.
I have a Mercurial repository hg-repo which has a directory cvs-dir that I want to simultaneously version control in CVS, and commit to a CVS repository:
$ ls hg-repo
cvs-dir other
The rest of the Mercurial repository such as other should not be bothered by CVS any how. How to set this up?
Edit
If I simply create a symbolic link (ln -s) to cvs-dir in a different CVS working copy directory cvs-repo
$ pwd
/home/foo
$ ls
hg-repo cvs-repo
$ ls -a cvs-repo
cvs-dir -> /home/foo/hg-repo/cvs-dir
then
do any CVS work from within /home/foo/cvs-repo such as committing the working copy to CVS repository;
write .cvsignore to ignore Mercurial meta data, and vice versa,
will this method have some potential problems?
This can help and is how I do this
First: Get the CVS repository locally.
Second: Create a mercurial repositories locally over this CVS repository. This will be used as your remote mercurial server.
Third: Clone this mercurial repository and do you work here.
Mercurial provides better merge support than cvs and will make your work easier. Commit back to CVS needs an extra step. Here is how this works, step-by-step. The workflow looks complicated, but is actually easy. Keep the flow-charts close.
Detailed step-by-step explanaition with flowchart
I can connect to my subversion server fine with Subclipse, but my commit is not working, and I'd like to add in some custom commands to make it work (I need to pass a un/pw). How can I set these parameters?
Right now the command it's setting is just
commit -m ""
I'd like it to be
commit -m --username <un> --password <pw>
Thanks.
Subversion will prompt you for username/password unless it has cached valid credentials. If you do not want to use those credentials, then you need to clear Subversion's cache. If using JavaHL, that means deleting the ~/.subversion/auth folder. On Windows, that is %APPDATA%\Subversion\auth
SVNKit caches credentials in the Eclipse keyring file.
I'm in the specific use case of wanting to methodologically document everything significant I do while setting up my new workstation (running Mac OS X Lion).
I would like to version control, in the same repository, files that are at totally different places on my file system, for instance files in /etc, ~/, /Libraries, etc.
Some thoughts/details on my requirements:
This repo will be for personal use only. I'll use a GUI client to browse my settings history.
I initially wanted to use Git, hosted in one large Github private repository, but as you can't clone subfolders the way you would do it with SVN, I'd have to create symlinks everywhere, which does not seem convenient.
So, would I be better off setting up a local SVN server and just checking in the files I want, when I want to version them?
You can use Mercurial, Git, ..., and then simply ignore all the files you don't want to version. Create the repository in the root and track the rest. Like (for Mercurial):
$ cd /
$ hg init
$ echo ".*" > .hgignore
$ echo '^(?!(etc|Libraries))' > .hgignore
$ hg add
$ hg commit -m "initial checkin"
An alternative is to use more specialized tools such as etckeeper that are made for tracking configuration data.
My CVS-fu is not very strong anymore (after years of SVN'ing and now Mercurial'ing). I'm trying to do a diff between two revisions of the HEAD branch (everything is in the HEAD anyway).
I received an IDE already set up to use a :pserver:myname#cvsserver:port/cvs/project CVS. I'm on Windows XP. I do not want to use the IDE (the goal here is to learn CVS a bit more).
Apparently I cannot login using SSH to the CVS server.
How can I run a remote CVS diff between two HEAD revs using the command line?
P.S: I am new here, mod me up so I can comment etc. :)
Is there any particular reason you want to learn more CVS after experiencing the wonders of SVN and Mercurial? In this industry, the opportunity cost of learning an outdated and difficult-to-use technology is that you forego the opportunity to learn something new and potentially more useful.
You may of course have a good reason, such as company requirements or other things outside of your control :(
With that said, this resource essentially serves as a CVS guidebook and a reference to many CVS command line tools. It looks like you can see differences between revisions on the HEAD, but only one file at a time.
http://kuparinen.org/martti/comp/cvs/cvs.html#8
[Show changes between two versions]
# cvs diff -u -r 1.42 -r 1.43 filename
# cvs diff -u -r BEFORE-XYZ -r HEAD [filename]