Mercurial > evolve
changeset 2726:70004f0847a2
amend: drop the implementation details from the user help
This is not relevant to users.
| author | Pierre-Yves David <pierre-yves.david@octobus.net> |
|---|---|
| date | Tue, 11 Jul 2017 11:12:23 +0200 |
| parents | 4eb90eace7f9 |
| children | f7d44441dfd3 |
| files | hgext3rd/evolve/evocommands.py tests/test-amend.t |
| diffstat | 2 files changed, 0 insertions(+), 12 deletions(-) [+] |
line wrap: on
line diff
--- a/hgext3rd/evolve/evocommands.py Tue Jul 11 10:55:06 2017 +0200 +++ b/hgext3rd/evolve/evocommands.py Tue Jul 11 11:12:23 2017 +0200 @@ -98,12 +98,6 @@ If you don't specify -m, the parent's message will be reused. - Behind the scenes, Mercurial first commits the update as a regular child - of the current parent. Then it creates a new commit on the parent's parents - with the updated contents. Then it changes the working copy parent to this - new combined changeset. Finally, the old changeset and its update are hidden - from :hg:`log` (unless you use --hidden with log). - Returns 0 on success, 1 if nothing changed. """ opts = opts.copy()
--- a/tests/test-amend.t Tue Jul 11 10:55:06 2017 +0200 +++ b/tests/test-amend.t Tue Jul 11 11:12:23 2017 +0200 @@ -132,12 +132,6 @@ If you don't specify -m, the parent's message will be reused. - Behind the scenes, Mercurial first commits the update as a regular child - of the current parent. Then it creates a new commit on the parent's - parents with the updated contents. Then it changes the working copy parent - to this new combined changeset. Finally, the old changeset and its update - are hidden from 'hg log' (unless you use --hidden with log). - Returns 0 on success, 1 if nothing changed. options ([+] can be repeated):