| commit | 4f35000df0668e9c3c4c1db0f691b5cf9d5df6bf | |
| author | Kyle J. McKay <mackyle@gmail.com> | |
| Mon, 23 Jan 2017 04:44:51 +0000 (22 20:44 -0800) | ||
| committer | Kyle J. McKay <mackyle@gmail.com> | |
| Mon, 23 Jan 2017 04:44:51 +0000 (22 20:44 -0800) | ||
| tree | daac5d3314ae9e3161442c83b5b4580882cfd668 | treesnapshot (tar.gz zip) |
| parent | 20439b1593689ceb6bac22072dbd3053fae3a4ac | commitdiff |
tg-create.sh: show `tg create --continue` to continue
Although the bare `tg create` is still accepted to continue a
`tg create ...` operation after resolving a merge conflict, Git
users are trained to use the `--continue` option to continue
after resolving merges.
Since `--continue` has been accepted for some time for just that
reason, show `tg create --continue` as the continuation command
to be more consistent with Git's behavior.
Signed-off-by: Kyle J. McKay <mackyle@gmail.com>
Although the bare `tg create` is still accepted to continue a
`tg create ...` operation after resolving a merge conflict, Git
users are trained to use the `--continue` option to continue
after resolving merges.
Since `--continue` has been accepted for some time for just that
reason, show `tg create --continue` as the continuation command
to be more consistent with Git's behavior.
Signed-off-by: Kyle J. McKay <mackyle@gmail.com>
| tg-create.sh | diffblobblamehistory |