Changes between Version 6 and Version 7 of WorkingWithGit

Timestamp:

Aug 20, 2016, 8:16:10 PM (8 years ago)

Author:

neverpanic (Clemens Lang)

Comment:

Add pushing.

WorkingWithGit

@@ -74 +74 @@
 which prompts you for the commit message. See the [#commitmessages section on commit messages in git] for more information on git conventions and expectations in commit messages.
 
+Because of Git's distributed nature, a commit on your local machine is not immediately available on the central server, like it was the case with Subversion. This means that you can continue to prepare further changes in additional commits before you publish your changes as a set. In fact, it is a very common practice in Git to do many small changes that are logically consistent in themselves and then publish them in one step.
+
+If you have commit access, you can publish your commits using `git push <remote-name> <branch-name>`. `<remote-name>` is the name of the repository to which you want to push. The most common push target is the location you initially cloned, which is automatically named `origin`. `<branch-name>` is the name of the branch you want to push. The Git equivalent to Subversion's `trunk` is called `master`. In most cases you do not need to specify `<remote-name>` or `<branch-name>`:
+{{{
+git push
+}}}
+
 
 == Common `git` tasks & notes about MacPorts' Subversion export ==