➜
This issue tracker has been migrated to GitHub,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
Created on 2011-04-18 16:09 by carljm, last changed 2022-04-11 14:57 by admin. This issue is now closed.
| Files | ||||
|---|---|---|---|---|
| File name | Uploaded | Description | Edit | |
| svn-like-wording.diff | carljm, 2011-04-18 16:09 | |||
| Messages (2) | |||
|---|---|---|---|
| msg133978 - (view) | Author: Carl Meyer (carljm) * | Date: 2011-04-18 16:09 | |
The opening paragraph of the "lifecycle of a patch" devguide page contains a confusing parenthetical aside implying that an "svn-like" workflow would mean never *saving* anything to your working copy and using "hg diff" to generate a patch. This is obviously wrong given the usual meaning of "save": if you never save anything to your working copy, "hg diff" will be empty. Patch attached with proposed alternative wording. |
|||
| msg133988 - (view) | Author: Ned Deily (ned.deily) *  |
Date: 2011-04-18 18:31 | |
Thanks for the improvement. Applied in changeset cc43ed7af5f2. |
|||
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2022-04-11 14:57:16 | admin | set | github: 56077 |
| 2011-04-18 18:31:51 | ned.deily | set | status: open -> closed nosy: + ned.deily messages: + msg133988 resolution: fixed stage: resolved |
| 2011-04-18 16:09:44 | carljm | create | |