mirror of
https://github.com/git/git
synced 2024-08-27 19:49:21 +00:00
Merge branch 'jm/doc-wording-tweaks'
* jm/doc-wording-tweaks: Documentation: wording fixes in the user manual and glossary
This commit is contained in:
commit
668668ad50
|
@ -1,7 +1,7 @@
|
|||
[[def_alternate_object_database]]alternate object database::
|
||||
Via the alternates mechanism, a <<def_repository,repository>>
|
||||
can inherit part of its <<def_object_database,object database>>
|
||||
from another object database, which is called "alternate".
|
||||
from another object database, which is called an "alternate".
|
||||
|
||||
[[def_bare_repository]]bare repository::
|
||||
A bare repository is normally an appropriately
|
||||
|
|
|
@ -416,12 +416,11 @@ REVISIONS" section of linkgit:gitrevisions[7].
|
|||
Updating a repository with git fetch
|
||||
------------------------------------
|
||||
|
||||
Eventually the developer cloned from will do additional work in her
|
||||
repository, creating new commits and advancing the branches to point
|
||||
at the new commits.
|
||||
After you clone a repository and commit a few changes of your own, you
|
||||
may wish to check the original repository for updates.
|
||||
|
||||
The command `git fetch`, with no arguments, will update all of the
|
||||
remote-tracking branches to the latest version found in her
|
||||
The `git-fetch` command, with no arguments, will update all of the
|
||||
remote-tracking branches to the latest version found in the original
|
||||
repository. It will not touch any of your own branches--not even the
|
||||
"master" branch that was created for you on clone.
|
||||
|
||||
|
@ -1811,8 +1810,8 @@ manner.
|
|||
You can then import these into your mail client and send them by
|
||||
hand. However, if you have a lot to send at once, you may prefer to
|
||||
use the linkgit:git-send-email[1] script to automate the process.
|
||||
Consult the mailing list for your project first to determine how they
|
||||
prefer such patches be handled.
|
||||
Consult the mailing list for your project first to determine
|
||||
their requirements for submitting patches.
|
||||
|
||||
[[importing-patches]]
|
||||
Importing patches to a project
|
||||
|
|
Loading…
Reference in a new issue