A local branch helps with this task by providing a (local) name by which the "current" commit can be found.

updating eclipse 3 3 to 3 4-42

Whenever a change to a (local) Repository is committed, a new commit object is created.

Without any other means, it would be very difficult to keep track of the changes in the Repository, in particular when other commits are added to the Repository, for example due to an update from the remote Repository or when checking out another commit.

If you're new to Git or distributed version control systems generally, then you might want to read Git for Eclipse Users first.

More background and details can be found in the on-line book Pro Git.

Trust Git provides a built-in trust chain through secure SHA-1 hashes which allows it to verify if objects obtained from a (potentially untrusted) source are correct and have not been modified since they have been created. The Git Index is a binary file stored in the directory containing a sorted list of file names, file modes, and file meta data used to efficiently detect file modifications.

It also contains the SHA-1 object names of blob objects.The working directory is the directory used to modify files for the next commit.By default it is located one level above the directory.You stage the modified files into the index and then commit the staged changes. This lifecycle is illustrated here: When setting up Git Repositories with EGit, there are two recommendations for the creation of "productive" (as opposed to "playground") Repositories: The first mistake happens when you specify a workspace folder during cloning or creation of a Repository.Both mistakes will happen when you use the Git Sharing Wizard from an Eclipse project that you have created manually in your workspace without taking precautions (the wizard has been fixed in the latest version).You will have to restart Eclipse for it to recognize the HOME value.