Minor cleanup in 10.2 regarding new tree creation and in 5.2 to explain format of return message from push. #782
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Added some additional information in 5.2 (Distributed Git - Contributing to a Project), to explain the format of the return message from the "git push" operation. Namely, a brief explanation of the .. fromref -> toref. I think this might be helpful to understand to rest of the discussion in the section. Thanks. |
td2014
changed the title
ben
reviewed
Oct 9, 2017
| The last line of the output above shows a useful return message from the push operation. | ||
| The basic format is `<oldref>..<newref> fromref \-> toref`, where `oldref` means the old reference, `newref` means the new reference, `fromref` is the name of the local reference being pushed, and `toref` is the name of the remote reference being updated. | ||
| You'll see similar output like this below in the discussions, so having a basic idea of the meaning will help in understanding the various states of the repositories. | ||
| More details are available in the documentation for https://git-scm.com/docs/git-push[git push]. |
There was a problem hiding this comment.
Can you change the link text to "git-push"? That's how you'd get the man page.
There was a problem hiding this comment.
@ben . Your requested change has been made. Thanks.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As I was reading section 10.2 regarding git internals and tree creation, I found what I think might be a minor omission of an "--add" flag and a superfluous "update-index" statement. I provide what I believe is a more streamlined and corrected version in this PR. Thanks.