Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

10.5 "Git Internals - The Refspec" misleading about what "refspecs" are #1999

Open
5 tasks done
Chealer opened this issue Dec 16, 2024 · 0 comments
Open
5 tasks done
Labels

Comments

@Chealer
Copy link

Chealer commented Dec 16, 2024

There's no existing/similar bug report.

  • I have searched the existing issues

This report is about a single actionable bug.

  • I'm reporting a single actionable bug

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:

  1. 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".
  2. 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

@Chealer Chealer added the bug label Dec 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant