git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 66/66] Use imperative form in help usage to describe an action

From
DNDrew Northup <n1xim.email@gmail.com>
Date
Aug 22, 2012, 18:32 UTC
Message-ID
<CAM9Z-nmrtU_a1v_4C_j=YAF7_HZ4+hGnBUcp969JfAbSXgUBig@mail.gmail.com>
In-Reply-To
<1345465975-16927-67-git-send-email-pclouds@gmail.com>
On Mon, Aug 20, 2012 at 8:32 AM, Nguyễn Thái Ngọc Duy <pclouds@gmail.com> wrote:
Show 5 quoted lines
>
> Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
> ---
>  My guts tell me this is correct, but my English foundation is shaking
>  so I say "change in the name of consistency"!

Your gut is working just fine. I haven't attempted to apply the patch, but the English changes check out just fine. It could be argued that these all should have taken the imperative form from the beginning as the user is directing the program to do something (perhaps vicariously via the documentation).

The other perspective I can think of off hand is that the documentation is describing what the program options do to the user (a different "audience")--which explains why the text wasn't in imperative form to begin with.

-- 
-Drew Northup
--------------------------------------------------------------
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS NewsBites Vol. 12 Num. 59
Previous: Nguyễn Thái Ngọc DuyNext: Junio C Hamano
Message 68 of 69 in “parseopt i18n marking (again)”
  1. 00/66 parseopt i18n marking (again)Nguyễn Thái Ngọc Duy, Aug 20, 2012
  2. 01/66 i18n: mark "style" in OPT_COLUMN() for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  3. 02/66 i18n: archive: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  4. 03/66 i18n: add: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  5. 04/66 i18n: bisect--helper: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  6. 05/66 i18n: blame: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  7. 06/66 i18n: branch: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  8. 07/66 i18n: cat-file: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  9. 08/66 i18n: check-attr: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  10. 09/66 i18n: checkout-index: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  11. 10/66 i18n: checkout: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  12. 11/66 i18n: cherry: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  13. 12/66 i18n: clean: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  14. 13/66 i18n: clone: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  15. 14/66 i18n: column: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  16. 15/66 i18n: commit: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  17. 16/66 i18n: config: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  18. 17/66 i18n: count-objects: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  19. 18/66 i18n: describe: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  20. 19/66 i18n: fast-export: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  21. 20/66 i18n: fetch: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  22. 21/66 i18n: fmt-merge-msg: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  23. 22/66 i18n: for-each-ref: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  24. 23/66 i18n: format-patch: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  25. 24/66 i18n: fsck: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  26. 25/66 i18n: gc: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  27. 26/66 i18n: grep: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  28. 27/66 i18n: hash-object: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  29. 28/66 i18n: help: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  30. 29/66 i18n: init-db: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  31. 30/66 i18n: log: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  32. 31/66 i18n: ls-files: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  33. 32/66 i18n: ls-tree: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  34. 33/66 i18n: merge-base: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  35. 34/66 i18n: merge-file: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  36. 35/66 i18n: merge: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  37. 36/66 i18n: mktree: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  38. 37/66 i18n: mv: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  39. 38/66 i18n: name-rev: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  40. 39/66 i18n: notes: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  41. 40/66 i18n: pack-objects: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  42. 41/66 i18n: pack-refs: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  43. 42/66 i18n: prune-packed: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  44. 43/66 i18n: prune: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  45. 44/66 i18n: push: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  46. 45/66 i18n: read-tree: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  47. 46/66 i18n: remote: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  48. 47/66 i18n: replace: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  49. 48/66 i18n: status: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  50. 49/66 i18n: rerere: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  51. 50/66 i18n: reset: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  52. 51/66 i18n: rev-parse: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  53. 52/66 i18n: revert, cherry-pick: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  54. 53/66 i18n: rm: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  55. 54/66 i18n: shortlog: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  56. 55/66 i18n: show-branch: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  57. 56/66 i18n: show-ref: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  58. 57/66 i18n: symbolic-ref: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  59. 58/66 i18n: tag: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  60. 59/66 i18n: update-index: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  61. 60/66 i18n: update-ref: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  62. 61/66 i18n: update-server-info: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  63. 62/66 i18n: verify-pack: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  64. 63/66 i18n: verify-tag: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  65. 64/66 i18n: write-tree: mark parseopt strings for translationNguyễn Thái Ngọc Duy, Aug 20, 2012
  66. 65/66 Reduce translations by using same terminologiesNguyễn Thái Ngọc Duy, Aug 20, 2012
  67. 66/66 Use imperative form in help usage to describe an actionNguyễn Thái Ngọc Duy, Aug 20, 2012
  68. Drew NorthupAug 22, 2012
  69. Junio C HamanoAug 20, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.