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

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

From
BBBráulio Bhavamitra <brauliobo@gmail.com>
Date
May 29, 2013, 18:11 UTC
Message-ID
<CAJri6_tm=tk6L1DT=A_BB25jm7b+2Uniw1uSCGtrY5_8X=t_hw@mail.gmail.com>
In-Reply-To
<f611150e-a12a-47f6-97f0-8aaff3045338@googlegroups.com>
---------- Forwarded message ----------
From: Bráulio Bhavamitra <brauliobo@gmail.com>
Date: Wed, May 29, 2013 at 8:23 AM
Subject: [git-users] Highlevel (but simple to implement) commands
provided by default for git
To: git-users@googlegroups.com
Hello all,

One of the things I note about git is that is provides mostly low-level and strictly necessary commands. Many highlevel commands are then implemented as alias by users, after a deep search on the internet.

Adding highlevel commands, even though it could be implemented by a simple alias, would put git in another level of user experience and create a new standard for newbie users. What git developers think about this?

I have, as many other users, an enormous .gitconfig. I paste here some highlevel commands of it, according to my judgement. Mercurial provides many of these highlevel commands.

  root = rev-parse --show-toplevel
 upstream = !git for-each-ref --format='%(upstream:short)' $(git
symbolic-ref -q HEAD)
 upstream-remote = !git upstream | sed -e 's/\\/.*$//g'
 out = !git fetch `git upstream-remote` && git l `git upstream`..HEAD
 in = pull --dry-run
 unmerged = !git ls-files --unmerged | cut -f2 | uniq
 untracked = ls-files --other --exclude-standard
 staged = ls-files --staged
 modified = ls-files --modified
 deleted = ls-files --deleted
  head = !git l -1
 current = rev-parse --abbrev-ref HEAD
Source: https://github.com/brauliobo/gitconfig/blob/master/configs/.gitconfig

regards, bráulio

-- You received this message because you are subscribed to the Google Groups "Git for human beings" group. To unsubscribe from this group and stop receiving emails from it, send an email to git-users+unsubscribe@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.

Previous: Bráulio BhavamitraNext: Ramkumar Ramachandra
Message 2 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.