git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Bráulio Bhavamitra" <brauliobo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: git-users-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
	git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: Highlevel (but simple to implement) commands provided by default for git
Date: Wed, 29 May 2013 15:05:52 -0300	[thread overview]
Message-ID: <CAJri6_vdN6-z0xvS2PrrdcesStqRKt7ve4dp8S2np3v=_S_ifg@mail.gmail.com> (raw)
In-Reply-To: <f611150e-a12a-47f6-97f0-8aaff3045338-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2154 bytes --]

On Wed, May 29, 2013 at 8:23 AM, Bráulio Bhavamitra <brauliobo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>wrote:

> 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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> For more options, visit https://groups.google.com/groups/opt_out.
>
>
>

-- 
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-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
For more options, visit https://groups.google.com/groups/opt_out.



[-- Attachment #2: Type: text/html, Size: 6933 bytes --]

       reply	other threads:[~2013-05-29 18:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f611150e-a12a-47f6-97f0-8aaff3045338@googlegroups.com>
     [not found] ` <f611150e-a12a-47f6-97f0-8aaff3045338-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2013-05-29 18:05   ` Bráulio Bhavamitra [this message]
2013-05-29 18:11 ` Fwd: [git-users] Highlevel (but simple to implement) commands provided by default for git Bráulio Bhavamitra
2013-05-29 18:26   ` Ramkumar Ramachandra
2013-05-29 19:50     ` Felipe Contreras
2013-05-29 20:00       ` Ramkumar Ramachandra
2013-05-30  2:48         ` Felipe Contreras
2013-05-29 20:07       ` Junio C Hamano
2013-05-29 20:19         ` Ramkumar Ramachandra
2013-05-29 21:15           ` Junio C Hamano
2013-05-29 21:26             ` Ramkumar Ramachandra
2013-06-02 19:20               ` Junio C Hamano
2013-06-03 23:22         ` Duy Nguyen
2013-05-29 18:58   ` Fwd: " Junio C Hamano
2013-05-29 19:39   ` Felipe Contreras
2013-05-29 20:27     ` Ramkumar Ramachandra
     [not found]       ` <CAJri6_uScqjovt5eK9f9+Z4ehtsdYQNuiEX1MERiDBEJWueAXg@mail.gmail.com>
2013-05-29 21:32         ` Ramkumar Ramachandra
2013-05-29 23:43           ` Jonathan Nieder
2013-05-30  3:08             ` Felipe Contreras
2013-05-30  5:23               ` Jonathan Nieder
2013-05-30  5:28                 ` Felipe Contreras
2013-05-30 14:54                   ` Jonathan Nieder
2013-05-30 15:32                     ` Felipe Contreras
2013-05-30  7:30             ` Ramkumar Ramachandra
2013-05-30  3:04       ` Felipe Contreras

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAJri6_vdN6-z0xvS2PrrdcesStqRKt7ve4dp8S2np3v=_S_ifg@mail.gmail.com' \
    --to=brauliobo-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=git-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=git-users-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).