User:Aaeinstein54

{Git aaeinstein repository}

Overview
It you're new to Git or distributed version control systems generally, then you may as being human make a decision by forming a git repository for its related tissues below to see if the simulation is close enough to actuate a comparison of the assumption then compare the issues that define a solution for a git repository. If you need more details and background read: https://guides.github.com/features/issues/

Identifying yourself
Whenever the history of the repository is changed (technically, whenever a commit is created), Git keeps track of the user who created that commit. The identification consists of a name (typically a person's name) and an e-mail address. This information is stored in file  under dedicated keys.

EGit will ask you for this information when you create your first commit. By default, this dialog is shown only once until you create a new workspace or tick the checkbox "Show initial configuration dialog" on the Git Preference page:

FILE:EGIT-0.11GETSTARTED-HISTORY 1.PNG

You can also untick "Don't show this dialog again" if you want to see it again later.

Instead of using this dialog, you can always change this information using the Git configuration: https://git-scm.com/docs/git-config


 * Click Preferences &gt; Team &gt; Git &gt; Configuration
 * Click New Entry and enter the key value pairs  and

Running Gaussian/Unix-based)www.Gaussian.com/g_tech_ur/m_running.htm

Setting up the Home Directory on Windows
Add the environment variable  to your environment variables.


 * 1) In Windows 7, type "enviroment window" at the start menu
 * 2) Select "Edit environment variables for your account"
 * 3) Click the "New" button.
 * 4) Enter "HOME" in the name field
 * 5) Enter "%USERPROFILE%" or some other path in the value field.
 * 6) Click OK, and OK again. You have just added the Home directory on Windows.

EGit needs this path for looking up the user configuration (.gitconfig). should point to your home directory e.g. . Ensure correct case! E.g.   instead of   may cause problems!

If the  variable is not defined the home directory will be calculated by concatenating   and.

If both  and   are not defined   will be used.

EGit shows a warning if  is not defined explicitly:

= Getting To Git Setup Time =

Firsthand Git Setup
Firsthand now that you have Git on your system How about doing a few things to print out your virtual Git environment You should only have to do these things once on any mobile laptop or desktop PC that will continue to be around during upgrades You can affordably change them at any time by running through the commands above

Git comes with a tool called   that lets you set configuration variables that control all aspects of how Git looks and operates These variables can be stored in three different places: Each level overrides values in the previous level, so values in  trump those in .
 * 1)   file: Contains values for every user on the system and all their repositories. If you pass the option   to , it reads and writes from this file specifically.
 * 2)   or   file: Specific to your user. You can make Git read and write to this file specifically by passing the   option.
 * 3)   file in the Git directory (that is,  ) of whatever repository you’re currently using: Specific to that single repository.

On Windows systems, Git looks for the   file in the   directory (  for most people). It also still looks for , although it’s relative to the MSys root, which is wherever you decide to install Git on your Windows system when you run the installer. If you are using version 2.x or later of Git for Windows, there is also a system-level config file at  on Windows XP, and in   on Windows Vista and newer. This config file can only be changed by   as an admin.

Your Identity
The first thing you should do when you install Git is to set your user name and email address. This is important because every Git commit uses this information, and it’s immutably baked into the commits you start creating: git config --global user.name git config --global user.email johndoe@example.com Again, you need to do this only once if you pass the   option, because then Git will always use that information for anything you do on that system. If you want to override this with a different name or email address for specific projects, you can run the command without the   option when you’re in that project.

Many of the GUI tools will help you do this when you first run them.

Your Editor
Now that your identity is set up, you can configure the default text editor that will be used when Git needs you to type in a message. If not configured, Git uses your system’s default editor.

If you want to use a different text editor, such as Emacs, you can do the following: git config --global core.editor emacs While on a Windows system, if you want to use a different text editor, such as Notepad++, you can do the following:

On a x86 system git config --global core.editor On a x64 system git config --global core.editor

NOTE
Vim, Emacs and Notepad++ are popular text editors often used by developers on Unix based systems like Linux and OS X or a Windows system. If you are not familiar with either of these editors, you may need to search for specific instructions for how to set up your favorite editor with Git.

WARNING
You may find, if you don’t setup an editor like this, you will likely get into a really confusing state when they are launched. Such example on a Windows system may include a prematurely terminated Git operation during a Git initiated edit.

Checking Your Settings
If you want to check your settings, you can use the  command to list all the settings Git can find at that point: git config --list You may see keys more than once, because Git reads the same key from different files (  and , for example). In this case, Git uses the last value for each unique key it sees.

You can also check what Git thinks a specific key’s value is by typing  : git config user.name prev | next

This open sourced site is hosted on GitHub.

Patches, suggestions and comments are welcome.

Git is a member of Software Freedom Conservancy

Create Repository

 * Create a new Java project


 * Select the project, click File &gt; Team &gt; Share Project
 * Select repository type Git and click Next


 * To configure the Git repository select the new project


 * Click Create Repository to initialize a new Git repository for the  project. If your project already resides in the working tree of an exisiting Git repository the repository is chosen automatically.


 * Click Finish to close the wizard.
 * The decorator text "&#91;master&#93;" behind the project shows that this project is tracked in a repository on the master branch and the question mark decorators show that the  and   and the   files are not yet under version control

Track Changes

 * Click Team &gt; Add on the project node
 * The + decorators show that now the project's files have been added to version control


 * Mark the "bin" folder as "ignored by Git", either by right-clicking on it and selecting Team &gt; Ignore or by creating a file  in the project folder with the following content

/bin


 * This excludes the  folder from Git's list of tracked files.
 * Add  to version control (Team &gt; Add):


 * Click Team &gt; Commit in the project context menu
 * Enter a commit message explaining your change, the first line (followed by an empty line) will become the short log for this commit. By default the author and committer are taken from the  file in your home directory.
 * You may click Add Signed-off-by to add a Signed-off-by: tag.
 * If you are committing the change of another author you may alter the author field to give the name and email address of the author.
 * Click Commit to commit your first change.


 * Note that the decorators of the committed files changed.

Inspect History

 * Click Team &gt; Show in History from the context menu to inspect the history of a resource


 * Create a new Java class  and implement it
 * Add it to version control and commit your change
 * Improve your implementation and commit the improved class
 * The resource history should now show 2 commits for this class


 * Click the Compare Mode toggle button in the History View
 * Double click  in the Resource list of the History View to open your last committed change in the Compare View

Congratulations, you just have mastered your first project using Git !

Create Local Repository

 * follow GitLab to create a new local repository (with your content instead of the demo project)

Create Repository at GitHub

 * create a new repository at GitHub

On the next screen you can see the URLs you may use to access your fresh new repository:
 * click SSH to choose the SSH protocol. It can be used for read and write access
 * click HTTP to choose the HTTP protocol. It can also be used for read and write access.
 * click Git Read-Only to choose the anonymous git protocol for cloning. It's the most efficient protocol git supports. Since the git protocol doesn't support authentication it's usually used to provide efficient read-only access to public repositories.

Eclipse SSH Configuration

 * Open the Eclipse Preferences and ensure that your SSH2 home is configured correctly (usually this is ~/.ssh) and contains your SSH2 keys


 * if you don't have SSH keys yet you may generate them on the second tab Key Management of this dialog, use a good pass phrase to protect your private key, for more details see "working with key passphrases"
 * upload your public SSH key to your GitHub account settings

Push Upstream

 * Click Team &gt; Remote &gt; Push... and copy and paste the SSH URL of your new github repository
 * If you are behind a firewall which doesn't allow SSH traffic use the github HTTPS URL instead and provide your github user and password instead of using the uploaded public SSH key. To store your credentials into the Eclipse secure store click Store in Secure Store.
 * Note: many HTTP proxies are configured to block HTTP URLs containing a user name, since disclosing a user name in an HTTP URL is considered a security risk. In that case remove the username from the HTTP URL and only provide it in the user field. It will be sent as an HTTP header.


 * Click Next and on first connection accept GitHub's host key.


 * Enter your SSH key's passphrase and click OK.


 * On the next wizard page click Add all branches spec to map your local branch names 1:1 to the same branch names in the destination repository.


 * Click Next. The push confirmation dialog will show a preview of the changes that will be pushed to the destination repository.


 * Click Finish to confirm that you want to push these changes.


 * The next dialog reports the result of the push operation.


 * Point your browser at your GitHub repository to see that your new repository content has arrived

EGit Tutorial (EclipseCon March 2011)
You may want to learn how to work with EGit and Gerrit Code Review by going through the EGit tutorial we held at EclipseCon America 2011.

Installation and Configuration
This tutorial was developed using EGit 0.11 so you should use at least this version. Newer versions may provide an easier way to do certain steps, look at the EGit "New and Noteworthy" documentation.

Best you go through the exercises using the Gerrit-in-a-zip you may download from TODO. See exercise 9 to learn how to use that.

The egit-training repository is also available on http://egit.eclipse.org/. You may clone it from there using git://egit.eclipse.org/egit-training.git

More details are given in
 * Exercise 1: Installation and configuration
 * Exercise 9: Starting demo Gerrit server

Exercises

 * Exercise 2: Develop a feature
 * Exercise 3: Review a change from another developer
 * Exercise 4: Rework your change
 * Exercise 5: Review re-worked change
 * Exercise 6: Register projects to watch
 * Exercise 7: Rebase change to resolve conflicts
 * Exercise 8: Working with patch series

EGit Tutorial (EclipseCon Europe Nov 2011)
We held this tutorial "Eclipse Hacker's Guide to the Git Universe" at EclipseCon Europe on Nov 2, 2011.

This tutorial was developed using EGit 1.2-SNAPSHOT so you should use at least this version. Newer versions may provide an easier way to do certain steps, look at the EGit "New and Noteworthy" documentation.

The egit-training repository is also available on http://egit.eclipse.org/. You may clone it from there using git://egit.eclipse.org/egit-training.git

Exercises
Find slides and exercises here