index 7892244ef19d507379489de0cc81ad18b936c6af..c5d5596d895755d69c8060bc38a800d7c70eda26 100644 (file)
This merges the changes from Bob's "master" branch into Alice's
current branch. If Alice has made her own changes in the meantime,
This merges the changes from Bob's "master" branch into Alice's
current branch. If Alice has made her own changes in the meantime,
-then she may need to manually fix any conflicts. (Note that the
-"master" argument in the above command is actually unnecessary, as it
-is the default.)
+then she may need to manually fix any conflicts.
The "pull" command thus performs two operations: it fetches changes
from a remote branch, then merges them into the current branch.
The "pull" command thus performs two operations: it fetches changes
from a remote branch, then merges them into the current branch.
then merged back together, the order in which 'git-log' presents
those commits is meaningless.
then merged back together, the order in which 'git-log' presents
those commits is meaningless.
-Most projects with multiple contributors (such as the linux kernel,
+Most projects with multiple contributors (such as the Linux kernel,
or git itself) have frequent merges, and 'gitk' does a better job of
visualizing their history. For example,
or git itself) have frequent merges, and 'gitk' does a better job of
visualizing their history. For example,
* linkgit:git-format-patch[1], linkgit:git-am[1]: These convert
series of git commits into emailed patches, and vice versa,
* linkgit:git-format-patch[1], linkgit:git-am[1]: These convert
series of git commits into emailed patches, and vice versa,
- useful for projects such as the linux kernel which rely heavily
+ useful for projects such as the Linux kernel which rely heavily
on emailed patches.
* linkgit:git-bisect[1]: When there is a regression in your
on emailed patches.
* linkgit:git-bisect[1]: When there is a regression in your