Do not loose commit history when specifying summary manually.
Review Request #7806 — Created Dec. 14, 2015 and discarded
When submitting multiple commits with one request on ReviewBoard RBTools sets the last commit message as the summary. But, when using the option "--summary” the last commit message is lost and is not written anywhere.
Proposed change stores all commit messages in the description field when both --summary 'text’ and --guess-description options are set.
When a request is send without the "--summary” option the last commit message is written in the summary, as usual.
When a request is send with the "--summary” option the last commit message is written in the description.
When a request is one commit without option "--summary” last commit message is written in the summary, as usual.
When a request comprises one commit then all works as usual.
| Description | From | Last Updated |
|---|---|---|
|
Col: 80 E501 line too long (86 > 79 characters) |
 reviewbot
|
|
|
Col: 80 E501 line too long (119 > 79 characters) |
reviewbot
|
|
|
Col: 27 E111 indentation is not a multiple of four |
reviewbot
|
|
|
Col: 1 W293 blank line contains whitespace |
reviewbot
|
|
|
Col: 80 E501 line too long (86 > 79 characters) |
reviewbot
|
|
|
Col: 80 E501 line too long (121 > 79 characters) |
reviewbot
|
|
|
Col: 122 W291 trailing whitespace |
reviewbot
|
|
|
Col: 80 E501 line too long (86 > 79 characters) |
reviewbot
|
|
|
Col: 80 E501 line too long (121 > 79 characters) |
reviewbot
|
Tool: Pyflakes Processed Files: rbtools/commands/post.py Tool: PEP8 Style Checker Processed Files: rbtools/commands/post.py