You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This report is about the ProGit book, version 2, English language.
This bug is not about a translation or old version
Bug covers book website/pdf
I confirm the bug is about the book as found on the website/pdf
Problem is present in the Pro Git book on the website?
This bug also affects the Pro Git book as published on the website.
Which version of the book is affected?
Source files
Describe the bug:
Section 10.5 Git Internals - The Refspec of the book can be misleading/confusing about "refspecs". I did not know/remember anything about refspecs last week, but visibly, the title itself has a couple issues:
The section itself has several mentions of "multiple refspecs" as well as the "default refspec", so the title should visibly read "Refspecs", not "The Refspec".
A look at git pull --help suffices to see several leaks (more than 5 references to refspecs as of Git 2.47). If refspecs were meant to be an internal, they are clearly far from having reached that status.
Of course, defining refspecs would help.
Steps to reproduce:
This does not report a behavioral bug.
Expected behavior:
This does not report a behavioral bug.
Screenshots:
No response
Additional context:
No response
Device
No response
Operating system
No response
Browser/application + version
No response
The text was updated successfully, but these errors were encountered:
There's no existing/similar bug report.
This report is about a single actionable bug.
This report is about the ProGit book, version 2, English language.
Bug covers book website/pdf
Problem is present in the Pro Git book on the website?
Which version of the book is affected?
Source files
Describe the bug:
Section 10.5 Git Internals - The Refspec of the book can be misleading/confusing about "refspecs". I did not know/remember anything about refspecs last week, but visibly, the title itself has a couple issues:
git pull --help
suffices to see several leaks (more than 5 references to refspecs as of Git 2.47). If refspecs were meant to be an internal, they are clearly far from having reached that status.Of course, defining refspecs would help.
Steps to reproduce:
This does not report a behavioral bug.
Expected behavior:
This does not report a behavioral bug.
Screenshots:
No response
Additional context:
No response
Device
No response
Operating system
No response
Browser/application + version
No response
The text was updated successfully, but these errors were encountered: