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

Re: [git-users] Highlevel (but simple to implement) commands provided by default for git

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
May 30, 2013, 15:32 UTC
Message-ID
<CAMP44s2G3NVUyVViF2NP0TEEuGLp-3z+xf-uhsjC-Np80WA-tA@mail.gmail.com>
In-Reply-To
<20130530145447.GC4884@elie.Belkin>
On Thu, May 30, 2013 at 9:54 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
Show 23 quoted lines
> Felipe Contreras wrote:
>> On Thu, May 30, 2013 at 12:23 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
>>> Felipe Contreras wrote:
>>>> On Wed, May 29, 2013 at 6:43 PM, Jonathan Nieder <jrnieder@gmail.com> wrote:
>
>>>>> A bigger problem (in my opinion) with allowing arbitrary changes to
>>>>> the meaning of existing commands is that scripts, whether placed in
>>>>> .sh files or given as commands to run over IRC, stop working
>>>>> altogether.  It's nice to have commands like "git log" and "git am"
>>>>> mean the same thing no matter what machine I am on.
>>>>
>>>> Except that's not true:
>>>
>>> It's not true that my opinion is that a bigger problem than the
>>> non-problem Ram mentioned with allowing arbitrary changes to the
>>> meaning of existing commands is that scripts stop working reliably?
>>
>> It's not true what you said:
>>
>> commands like "git log" and "git am" mean the same thing no matter
>> what machine I am on.
>
> It's not true that it's nice when they do?
Yeah, it's nice that the sun is purple. Never-mind the fact that it's not true.

The consistency you experience across machines has absolutely nothing to do with Git, since Git can be configured in a way you don't consider nice.

So this argument is invalid. Any proposed change to make Git more configurable is not affected by this argument, because Git can *already* be configured in a way that would break your experience, yet it doesn't happen.

In other words; it's the policy or your machine users you have to thank for, not Git's code, and changing Git's code is not going to change that policy.

Either way this is a straw man, again, nobody is pushing to allow builtins to be overridable.

The topic is default *aliases*.
-- 
Felipe Contreras
Previous: Jonathan NiederNext: Ramkumar Ramachandra
Message 23 of 24 in “Re: Highlevel (but simple to implement) commands provided by default for git”
  1. Bráulio BhavamitraMay 29, 2013
  2. Fwd: [git-users] Highlevel (but simple to implement) commands provided by default for gitBráulio Bhavamitra, May 29, 2013
  3. Ramkumar RamachandraMay 29, 2013
  4. Felipe ContrerasMay 29, 2013
  5. Ramkumar RamachandraMay 29, 2013
  6. Felipe ContrerasMay 30, 2013
  7. Junio C HamanoMay 29, 2013
  8. Ramkumar RamachandraMay 29, 2013
  9. Junio C HamanoMay 29, 2013
  10. Ramkumar RamachandraMay 29, 2013
  11. Junio C HamanoJun 2, 2013
  12. Duy NguyenJun 3, 2013
  13. Junio C HamanoMay 29, 2013
  14. Felipe ContrerasMay 29, 2013
  15. Ramkumar RamachandraMay 29, 2013
  16. Felipe ContrerasMay 30, 2013
  17. Ramkumar RamachandraMay 29, 2013
  18. Jonathan NiederMay 29, 2013
  19. Felipe ContrerasMay 30, 2013
  20. Jonathan NiederMay 30, 2013
  21. Felipe ContrerasMay 30, 2013
  22. Jonathan NiederMay 30, 2013
  23. Felipe ContrerasMay 30, 2013
  24. Ramkumar RamachandraMay 30, 2013

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.