Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Git | ||||||||
Line: 11 to 11 | ||||||||
A concise introduction to remote Git repositories for CVS users, which is the basis for many of these instructions, can be found at:
http://www.kernel.org/pub/software/scm/git/docs/gitcvs-migration.html![]() | ||||||||
Added: | ||||||||
> > | A good cheat sheet for commandline git users is available at:
https://git.wiki.kernel.org/index.php/GitCheatSheet![]() | |||||||
CVS repository"> Importing a CVS repository |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Git | ||||||||
Line: 103 to 103 | ||||||||
| ||||||||
Changed: | ||||||||
< < | Mercurial and Git | |||||||
> > | Eclipse and Git | |||||||
Changed: | ||||||||
< < | Git is popular. However, it doesn't always have the best UI. For example, the Eclipse plugin for Git is.... a work in progress. Fortunately, the MercurialEclipse plugin is a lot better (http://www.javaforge.com/project/HGE![]() ![]()
Mercurial+Git+WindowsIn principle it's also possible to have TortoiseHg (http://tortoisehg.bitbucket.org/![]() ![]() | |||||||
> > | Git is popular. However, it doesn't always have the best UI. For example, the Eclipse plugin for Git is not as polished as that for CVS. That said, it is under active development (Eclipse itself is switching to Git) and if you use Eclipse Helios, the plugin is usable for many common cases (you still may have to fall back to the command line for more complex merging tasks). | |||||||
-- ChrisNell - 23 Jun 2010 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Git | ||||||||
Line: 107 to 107 | ||||||||
Git is popular. However, it doesn't always have the best UI. For example, the Eclipse plugin for Git is.... a work in progress. Fortunately, the MercurialEclipse plugin is a lot better (http://www.javaforge.com/project/HGE![]() ![]() | ||||||||
Added: | ||||||||
> > |
| |||||||
Mercurial+Git+WindowsIn principle it's also possible to have TortoiseHg (http://tortoisehg.bitbucket.org/![]() ![]() |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Git | ||||||||
Line: 6 to 6 | ||||||||
Members of the klb group should have permissions to work with repositories located here. Important: creators of / committers to Git repositories hosted here should ensure their default umask is 027 at most, to ensure that other klb users can read, write, and search their additions! To do this, edit either ~/.bashrc or ~/.cshrc (depending on whether you use BASH or CSh by default) and add the line umask 027 . | ||||||||
Added: | ||||||||
> > | It is also a good idea, especially for windows code committers, to ensure they use Unix-style line endings. | |||||||
A concise introduction to remote Git repositories for CVS users, which is the basis for many of these instructions, can be found at:
http://www.kernel.org/pub/software/scm/git/docs/gitcvs-migration.html![]() |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Git | ||||||||
Line: 103 to 103 | ||||||||
Mercurial and Git | ||||||||
Changed: | ||||||||
< < | GIt is popular. However, it doesn't always have the best UI. For example, teh Eclipse plugin for Git is.... a work in progress. Fortunately, the MercurialEclipse plugin is a lot better (http://www.javaforge.com/project/HGE![]() ![]() | |||||||
> > | Git is popular. However, it doesn't always have the best UI. For example, the Eclipse plugin for Git is.... a work in progress. Fortunately, the MercurialEclipse plugin is a lot better (http://www.javaforge.com/project/HGE![]() ![]() | |||||||
Changed: | ||||||||
< < | I've also successfully made TortoiseHg (http://tortoisehg.bitbucket.org/![]() | |||||||
> > | Mercurial+Git+Windows | |||||||
Added: | ||||||||
> > | In principle it's also possible to have TortoiseHg (http://tortoisehg.bitbucket.org/![]() ![]() | |||||||
-- ChrisNell - 23 Jun 2010 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Git | ||||||||
Line: 77 to 77 | ||||||||
Added: | ||||||||
> > | Using TortoiseGit (Windows) with remote repositoriesIn order to install TortoiseGit: 1. Download and install Git for Windows from http://msysgit.googlecode.com/files/Git-1.7.0.2-preview20100309.exe![]() ![]()
You will need to provide SSH credentials for an account in klb group to access it. Remember to set the default umask of this account to (at most) 027, in order that others might see your work. NB: to set up a .ppk ssh key if you don't have one, see http://linux-sxs.org/networking/openssh.putty.html![]() TortoiseGit usage notes
| |||||||
Added: | ||||||||
> > | Mercurial and Git | |||||||
Added: | ||||||||
> > | GIt is popular. However, it doesn't always have the best UI. For example, teh Eclipse plugin for Git is.... a work in progress. Fortunately, the MercurialEclipse plugin is a lot better (http://www.javaforge.com/project/HGE![]() ![]() | |||||||
Added: | ||||||||
> > | I've also successfully made TortoiseHg (http://tortoisehg.bitbucket.org/![]() | |||||||
-- ChrisNell - 23 Jun 2010 |
Line: 1 to 1 | ||||||||
---|---|---|---|---|---|---|---|---|
Added: | ||||||||
> > |
GitWe have set up a common remote location for git repositories. These repositories are located on the netapp filesystem at/ubc/cs/project/arrow/git . Note that these should be bare remote repositories, and in particular should not have an associated working copy.
Members of the klb group should have permissions to work with repositories located here. Important: creators of / committers to Git repositories hosted here should ensure their default umask is 027 at most, to ensure that other klb users can read, write, and search their additions! To do this, edit either ~/.bashrc or ~/.cshrc (depending on whether you use BASH or CSh by default) and add the line umask 027 .
A concise introduction to remote Git repositories for CVS users, which is the basis for many of these instructions, can be found at:
http://www.kernel.org/pub/software/scm/git/docs/gitcvs-migration.html![]() CVS repository"> Importing a CVS repositoryThese instructions use the cvsimport script included with Git, and should be sufficient for migrating most papers, or other relatively simple repositories. A more powerful alternative involves use of cvs2git, and is not covered here. For example, to import a CVS repository located at/ubc/cs/project/arrow/cvs/PAPER to a Git repo at ubc/cs/project/arrow/git/PAPER :
1. Ensure your CVSROOT environment variable is set appropriately; eg:
2. (optional) Ensure relevant authorship info is configured by editing /ubc/cs/project/arrow/git/authors . Authors not listed therein will be referred to in all logs by their UNIX username rather than their full name/email.
3. Import the repository to a temporary location, say ~/myrepo :
4. Create the remote repository (see next section)
5. Remove the temporary repository (unless you want to keep it as a local working repo)
Creating a remote repository from an existing Git repository(Taken from http://www.kernel.org/pub/software/scm/git/docs/gitcvs-migration.html![]() ~/myrepo on a machine with UBC network access. Create a new "bare" repository and fetch your project into it:
Using TortoiseGit (Windows) with remote repositoriesIn order to install TortoiseGit: 1. Download and install Git for Windows from http://msysgit.googlecode.com/files/Git-1.7.0.2-preview20100309.exe![]() ![]()
You will need to provide SSH credentials for an account in klb group to access it. Remember to set the default umask of this account to (at most) 027, in order that others might see your work. NB: to set up a .ppk ssh key if you don't have one, see http://linux-sxs.org/networking/openssh.putty.html![]() TortoiseGit usage notes
|