'Documentation' is a tricky subject. Are the manuals for reference (i.e. looking up the specifics that you already understand) or for education, or training, or for examples, or concepts, philosophy and mental models, etc.
At the moment they (man pages) are primarily for reference, rather than explanation and education, while the git-scm book comes from a different direction. I'd agree that rebasing, and the man page, are tricky to navigate, and sometimes require extra coding or investigation to determine, for example commit-id ranges. The first main concept to get / understand is "upstream" (and if it's the same as your "publish" repo). You may find that your use case deviates to the 'expected' approach [I've just been there!]. Then it's identify the three IDs approach, along wit the `-i` interactive check. P. On Tuesday, November 30, 2021 at 3:55:27 PM UTC skybu...@hotmail.com wrote: > https://git-scm.com/book/en/v2/Git-Branching-Rebasing > > I believe git rebase must be done from the branch which is to be re-based. > > So it's always necessary to git switch <branch-to-rebase> > > It is not possible to go to git switch <master> > > and then do git rebase <branch-to-rebase> etc > > This will not work and go wrong correct ?!? > > If so, then the documentation at this link is not clear: > > https://git-scm.com/book/en/v2/Git-Branching-Rebasing > > There are some re-base commands without a clear git switch > <branch-to-rebase> > > This makes it seems like it's possible to issue this command from any > branch. > > Documentation should be updated and make clear that user has to been on > the branch that is to be rebased. > > Bye, > Skybuck. > -- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/git-users/1ccf4ac7-aa82-4798-9613-44578193437fn%40googlegroups.com.
