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

Re: EasyGit Integration

From
Sam Vilain <sam@vilain.net>
Date
Jun 10, 2009, 01:25 UTC
Message-ID
<4A2F0B8A.9010203@vilain.net>
In-Reply-To
<alpine.LFD.2.01.0906091512350.6847@localhost.localdomain>
Linus Torvalds wrote:
Show 16 quoted lines
> On Tue, 9 Jun 2009, Scott Chacon wrote:
>   
>> * breaks the various things that 'checkout' does into separate
>> commands - moves 'revert' to doing what 'checkout -- path' does
>>     
>
> No.
>
> NAK on this one. 
>
> The fact that some idiotic SVN usage exists is not an excuse to break 
> long-standing git users. "revert" comes from bk, and quite frankly, I 
> object _very_ strongly to taking naming from something that is very 
> obviously the inferior system (SVN) over something very obviously superior 
> (BK and git).
>

We talked about this much at GitTogether '08. It's true that for 'reverting' a change in the past, that is the right thing to do. However I don't think there is a first principles case that this is always what people mean by 'revert'. And it is not just SVN - Mercurial, Monotone, Bazaar, Darcs all use 'revert' in this way. By comparison with those systems, the number of users coming from BK is quite low.

We talked about making a 'git revert-file' and 'git revert-commit', with 'git revert' printing a message encouraging the user to specify which one they wanted (or potentially pointing them to the correct incantations of 'git checkout' or 'git cherry-pick').

I think as long as there is a deprecation cycle, and that users can select the old behaviour (either via an alias or a config option), then we shouldn't upset many long-time users of revert. Do you agree?

Sam.
Previous: Matthieu MoyNext: Linus Torvalds
Message 39 of 49 in “EasyGit Integration”
  1. Scott ChaconJun 9, 2009
  2. Nicolas PitreJun 9, 2009
  3. Avery PennarunJun 9, 2009
  4. Björn SteinbrinkJun 9, 2009
  5. Avery PennarunJun 9, 2009
  6. Björn SteinbrinkJun 10, 2009
  7. Elijah NewrenJun 9, 2009
  8. Miles BaderJun 10, 2009
  9. Björn SteinbrinkJun 9, 2009
  10. Elijah NewrenJun 9, 2009
  11. Björn SteinbrinkJun 9, 2009
  12. Björn SteinbrinkJun 9, 2009
  13. Junio C HamanoJun 9, 2009
  14. Elijah NewrenJun 9, 2009
  15. Elijah NewrenJun 9, 2009
  16. Matthieu MoyJun 10, 2009
  17. Linus TorvaldsJun 9, 2009
  18. Elijah NewrenJun 9, 2009
  19. Linus TorvaldsJun 9, 2009
  20. Mark LodatoJun 10, 2009
  21. Miles BaderJun 10, 2009
  22. Theodore TsoJun 10, 2009
  23. Linus TorvaldsJun 10, 2009
  24. Felipe ContrerasJun 10, 2009
  25. Linus TorvaldsJun 10, 2009
  26. Scott ChaconJun 10, 2009
  27. Jakub NarebskiJun 11, 2009
  28. Felipe ContrerasJun 11, 2009
  29. Jakub NarebskiJun 11, 2009
  30. Felipe ContrerasJun 12, 2009
  31. Jakub NarebskiJun 12, 2009
  32. Felipe ContrerasJun 12, 2009
  33. Jakub NarebskiJun 12, 2009
  34. Felipe ContrerasJun 12, 2009
  35. Björn SteinbrinkJun 13, 2009
  36. Felipe ContrerasJun 11, 2009
  37. Elijah NewrenJun 10, 2009
  38. Matthieu MoyJun 10, 2009
  39. Sam VilainJun 10, 2009
  40. Linus TorvaldsJun 10, 2009
  41. Junio C HamanoJun 10, 2009
  42. Sam VilainJun 10, 2009
  43. Jakub NarebskiJun 10, 2009
  44. Nicolas PitreJun 10, 2009
  45. Junio C HamanoJun 10, 2009
  46. Elijah NewrenJun 10, 2009
  47. Scott ChaconJun 10, 2009
  48. Felipe ContrerasJun 10, 2009
  49. Felipe ContrerasJun 10, 2009

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.