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

Re: Call Me Gitless

From
TTarmigan <tarmigan+git@gmail.com>
Date
Aug 19, 2008, 00:45 UTC
Message-ID
<905315640808181745n7186aa1bu62f6d454255fd805@mail.gmail.com>
In-Reply-To
<alpine.LNX.1.00.0808182027240.19665@iabervon.org>
On Mon, Aug 18, 2008 at 5:32 PM, Daniel Barkalow <barkalow@iabervon.org> wrote:
Show 26 quoted lines
> On Mon, 18 Aug 2008, Tarmigan wrote:
>
>> On Mon, Aug 18, 2008 at 1:20 PM, Junio C Hamano <gitster@pobox.com> wrote:
>> > (2) Some concepts in git are different from what they are used to, without
>> >    any good reason.  IOW, the concepts have room for improvement, and our
>> >    UI is based on these faulty concepts.
>> >
>> > (3) Some concepts in git may be exactly the same with other systems, yet
>> >    our UI may operate differently from them without any good reason.
>>
>> One confusing part of the porcelain may be the way that git's revert
>> is different from other systems' revert.  What would people think
>> about something like this somewhere in git-revert(1)?
>>
>> +DISCUSSION
>> +----------
>> +If you are more familiar with another SCM, 'git revert' may not do what you
>> +expect.  Specifically, if you want to throw away all changes in your working
>> +directory, you should read the man page for 'git reset', particulary the
>> +'--hard' option.  If you want to extract specific files as they were in a
>> +previous commit, you should read the man page for 'git checkout -- <filename>'.
>
> "as they were in a particular commit"; it works for the current commit as
> well as older ones. And skip the first sentence; even people who aren't
> familiar with another SCM are reasonably likely to be attracted by the
> name "revert" as being descriptive of what they want to do.
Good points, thanks.
> I think this is a good idea, although clever placement is necessary to
> neither distract people who really do want "revert" nor get missed by
> people who are looking in the wrong place.

Yes, I actually didn't include any context because I wasn't sure where to put it and was hoping for feedback on that front as well. git-revert(1) is very short as it is, so I would be inclined to put the DISCUSSION fairly early, like between the DESCRIPTION and the OPTIONS so it is very easy to find. But it seems incorrect to put it before the options. Perhaps that text should just be a note in the DESCRIPTION?

Thanks, Tarmigan

Previous: Daniel BarkalowNext: Peter Valdemar Mørch (Lists)
Message 49 of 67 in “Call Me Gitless”
  1. TransAug 18, 2008
  2. Benjamin SergeantAug 18, 2008
  3. Martin LanghoffAug 18, 2008
  4. Pascal ObryAug 18, 2008
  5. Jon LoeligerAug 18, 2008
  6. Daniel BarkalowAug 18, 2008
  7. Marcus GriepAug 18, 2008
  8. Junio C HamanoAug 18, 2008
  9. Daniel BarkalowAug 18, 2008
  10. Junio C HamanoAug 18, 2008
  11. Daniel BarkalowAug 18, 2008
  12. Junio C HamanoAug 19, 2008
  13. Marcus GriepAug 19, 2008
  14. Junio C HamanoAug 19, 2008
  15. Junio C HamanoAug 19, 2008
  16. diff: vary default prefix depending on what are comparedJunio C Hamano, Aug 20, 2008
  17. Jakub NarebskiAug 20, 2008
  18. Stephen R. van den BergAug 19, 2008
  19. Jakub NarebskiAug 19, 2008
  20. Junio C HamanoAug 19, 2008
  21. Jeff KingAug 19, 2008
  22. Daniel BarkalowAug 19, 2008
  23. Jeff KingAug 19, 2008
  24. Daniel BarkalowAug 19, 2008
  25. Jeff KingAug 19, 2008
  26. Daniel BarkalowAug 19, 2008
  27. Petr BaudisAug 19, 2008
  28. Daniel BarkalowAug 19, 2008
  29. Junio C HamanoAug 19, 2008
  30. Junio C HamanoAug 19, 2008
  31. Daniel BarkalowAug 19, 2008
  32. Sverre Hvammen JohansenAug 21, 2008
  33. Junio C HamanoAug 21, 2008
  34. 1/3 sha1_object_info(): pay attention to cached objectsJunio C Hamano, Aug 21, 2008
  35. 2/3 cached_object: learn empty blobJunio C Hamano, Aug 21, 2008
  36. 3/3 git-add --intent-to-add (-N)Junio C Hamano, Aug 21, 2008
  37. Paolo BonziniAug 21, 2008
  38. Jonathan NiederAug 21, 2008
  39. Jonathan NiederAug 22, 2008
  40. Daniel BarkalowAug 22, 2008
  41. Junio C HamanoAug 22, 2008
  42. Jonathan NiederAug 22, 2008
  43. Junio C HamanoAug 22, 2008
  44. Jonathan NiederAug 22, 2008
  45. Jonathan NiederAug 22, 2008
  46. Daniel BarkalowAug 21, 2008
  47. TarmiganAug 18, 2008
  48. Daniel BarkalowAug 19, 2008
  49. TarmiganAug 19, 2008
  50. Peter Valdemar Mørch (Lists)Aug 19, 2008
  51. Junio C HamanoAug 19, 2008
  52. Imran M YousufAug 19, 2008
  53. Peter Valdemar Mørch (Lists)Aug 19, 2008
  54. Imran M YousufAug 19, 2008
  55. Alexander E GenaudAug 19, 2008
  56. Matthieu MoyAug 19, 2008
  57. Mike HommeyAug 19, 2008
  58. Alexander E GenaudAug 19, 2008
  59. Pascal ObryAug 19, 2008
  60. Paolo BonziniAug 21, 2008
  61. Elijah NewrenAug 22, 2008
  62. Peter Valdemar Mørch (Lists)Aug 19, 2008
  63. Mark StrubergAug 19, 2008
  64. Alexander E GenaudAug 19, 2008
  65. Junio C HamanoAug 19, 2008
  66. Teemu LikonenAug 19, 2008
  67. Jakub NarebskiAug 19, 2008

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.