Recent discussions have shown that rebase isn't as well understood as
as perhaps it should be for the basic user. 

Add a softer introductory paragraph to the man page description, and
in the second patch, add a second paragraph explaining the build up of
the command so that users have a historical context in which to
rationalise the command structure.

The second patch/paragraph will probably need the quoting checking as
to which are quoting the generic command and which are the same text
as a command example.

Basic wording is borrowed from on-list clarifications.

Philip Oakley (2):
  Doc rebase: Describe rebase as excluding merge commits
  Doc rebase: describe the priority of published work

 Documentation/git-rebase.txt | 10 ++++++++++
 1 file changed, 10 insertions(+)


To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to
More majordomo info at

Reply via email to