Linux git configuration.

 

Win8 has carried too many expectations of Microsoft and hopes to unify the desktop PC and mobile phone market. It has also made a lot of moves and gimmicks. Just as my colleagues downloaded win8rc, they used the Virtual Machine VMware to try it out.

During installation, I was not shocked and amazed when I first installed Windows 7. When I entered it, I had heard of the square elements, and the default wallpaper didn't have any viewing experience of Windows 7. (Windows 7 default wallpaper has not been changed since now)

The idea that I tried it for 30 minutes is useless. It is a very risky thing to make such a big change in the UI. It can be said that it is a strong way of X user habits and experience, for example, I am very disgusted when no menu is started.

It is strongly felt that a great mobile phone company like Nokia has been pitted by Microsoft. With the virtue of Metro, it is hard to see the day of Nokia's revitalization.

Far away, I installed a new Ubuntu 12.04 with VMware. I felt like I was used to being strong X. Your uncle's unity did not do anything nice on the desktop, your uncle asked me to change the tools I used and found a bunch of people on the internet complaining. The solution is to install gnome by myself, but you can only install gnome3, however, this menu item lacks the network link and logout option, and does not want to be tossed. It is fixed to ubuntu10.10. (my colleague switched to linuxmint for a similar reason ). I encountered some problems in the GIT environment. Please record it later.

Description: Most of the following content comes from: https://github.com /.

1. Download git

 

$ apt-get install git-core

 

2. Configure personal information (not required ).

 

git config --global user.name "Your Name Here"git config --global user.email "your_email@youremail.com"

3. Set the password cache time.

/**To use this option, you need to tur*n on the credential helper so that git*will save your password in memory f*or some time:*/git config --global credential.helper cache# Set git to use the credential memory cache//By default git will cache your password for 15 minutes. You can change this if you like.git config --global credential.helper 'cache --timeout=3600'# Set the cache to timeout after 1 hour (setting is in seconds)

4. Configure the remote GitHub library SSH Password

First, we need to check for existing ssh keys on your computer. Open up Git Bash and run:cd ~/.ssh# Checks to see if there is a directory named ".ssh" in your user directorySince there is already an SSH directory you'll want to back the old one up and remove it:ls# Lists all the subdirectories in the current directory# config  id_rsa  id_rsa.pub  known_hostsmkdir key_backup# Makes a subdirectory called "key_backup" in the current directorycp id_rsa* key_backup# Copies the id_rsa keypair into key_backuprm id_rsa*# Deletes the id_rsa keypairTo generate a new SSH key, enter the code below. We want the default settings so when asked to enter a file in which to save the key, just press enter. ssh-keygen -t rsa -C "your_email@youremail.com"# Creates a new ssh key using the provided email# Generating public/private rsa key pair.# Enter file in which to save the key (/c/Users/you/.ssh/id_rsa): [Press enter]Now you need to enter a passphrase.Why do passphrases matter?# Enter passphrase (empty for no passphrase): [Type a passphrase]# Enter same passphrase again: [Type passphrase again]Which should give you something like this: # Your identification has been saved in /c/Users/you/.ssh/id_rsa.# Your public key has been saved in /c/Users/you/.ssh/id_rsa.pub.# The key fingerprint is:# 01:0f:f4:3b:ca:85:d6:17:a1:7d:f0:68:9d:f0:a2:db your_email@youremail.comStep 4: Add your SSH key to GitHubRun the following code to copy the key to your clipboard.clip < ~/.ssh/id_rsa.pub# Copies the contents of the id_rsa.pub file to your clipboardBe warned: it is important to copy the key exactly without adding newlines or whitespace. Thankfully the clip command makes it easy to perform this setup perfectly.Go to your Account SettingsClick "SSH Keys" in the left sidebarClick "Add SSH key"Paste your key into the "Key" fieldClick "Add key"Confirm the action by entering your GitHub password

5. Create a local code library

 

Step 1: Create the README fileIn the prompt, type the following code:mkdir ~/Hello-World# Creates a directory for your project called "Hello-World" in your user directorycd ~/Hello-World# Changes the current working directory to your newly created directorygit init# Sets up the necessary Git files# Initialized empty Git repository in /Users/you/Hello-World/.git/touch README# Creates a file called "README" in your Hello-World directoryStep 2: Commit your READMENow that you have your README set up, it's time to commit it. A commit is essentially a snapshot of all the files in your project at a particular point in time. In the prompt, type the following code:More about commitsgit add README# Stages your README file, adding it to the list of files to be committedgit commit -m 'first commit'# Commits your files, adding the message "first commit"Step 3: Push your commitSo far everything you've done has been in your local repository, meaning you still haven't done anything on GitHub yet. To connect your local repository to your GitHub account, you will need to set a remote for your repo and push your commits to it:More about remotesgit remote add origin https://github.com/username/Hello-World.git# Creates a remote named "origin" pointing at your GitHub repogit push origin master# Sends your commits in the "master" branch to GitHub

 

6. The GIT command cannot automatically complete the solution:

See the following blog: clickme!