From: Ramkumar Ramachandra <artagnon@gmail.com>
To: "Bráulio Bhavamitra" <brauliobo@gmail.com>
Cc: git@vger.kernel.org, Matthieu Moy <Matthieu.Moy@imag.fr>
Subject: Re: [git-users] Highlevel (but simple to implement) commands provided by default for git
Date: Wed, 29 May 2013 23:56:58 +0530 [thread overview]
Message-ID: <CALkWK0k8GkFYNkoGH4YCgmWtSR5rgFSG0dU9Aw2CO_arvuzKxQ@mail.gmail.com> (raw)
In-Reply-To: <CAJri6_tm=tk6L1DT=A_BB25jm7b+2Uniw1uSCGtrY5_8X=t_hw@mail.gmail.com>
Bráulio Bhavamitra wrote:
> root = rev-parse --show-toplevel
What is your usecase for this?
> upstream = !git for-each-ref --format='%(upstream:short)' $(git
> symbolic-ref -q HEAD)
Again, what is the usecase? What doesn't @{u} do?
> upstream-remote = !git upstream | sed -e 's/\\/.*$//g'
Windows back-slashes?
> out = !git fetch `git upstream-remote` && git l `git upstream`..HEAD
I didn't understand this at all. What are you doing?
> in = pull --dry-run
Why?
> 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
What is wrong with git status showing a unified output?
> head = !git l -1
What is git l again?
> current = rev-parse --abbrev-ref HEAD
Why don't you use a prompt? Use the one in contrib/completion/git-prompt.sh.
next prev parent reply other threads:[~2013-05-29 18:27 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 ` Highlevel (but simple to implement) commands provided by default for git Bráulio Bhavamitra
2013-05-29 18:11 ` Fwd: [git-users] " Bráulio Bhavamitra
2013-05-29 18:26 ` Ramkumar Ramachandra [this message]
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=CALkWK0k8GkFYNkoGH4YCgmWtSR5rgFSG0dU9Aw2CO_arvuzKxQ@mail.gmail.com \
--to=artagnon@gmail.com \
--cc=Matthieu.Moy@imag.fr \
--cc=brauliobo@gmail.com \
--cc=git@vger.kernel.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).