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

[Felipe Contreras <felipe.contreras@gmail.com>]

On Wed, May 29, 2013 at 1:26 PM, Ramkumar Ramachandra
<artagnon@gmail.com> wrote:
> Bráulio Bhavamitra wrote:
>>   root = rev-parse --show-toplevel
>
> What is your usecase for this?

Some Git commands expect to be in the top level directory (e.g. git blame).

>>  upstream-remote = !git upstream | sed -e 's/\\/.*$//g'
>
> Windows back-slashes?

Maybe git config quoting.

>>  out = !git fetch `git upstream-remote` && git l `git upstream`..HEAD
>
> I didn't understand this at all.  What are you doing?

Finding out what changes haven't been pushed out yet?

>>  in = pull --dry-run
>
> Why?

Because it's very easy to mess things up with 'git pull'. This
probably wouldn't be needed if we change the default of 'git pull' to
barf when the changes are not a fast-forward, and print a message
suggesting to either merge or rebase, as it has been suggested.

>>  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?

It's not easy to be used in "scripts", say, 'gvim -p $(git unmerged)'.

>>   head = !git l -1
>
> What is git l again?

'git log', of course.

>>  current = rev-parse --abbrev-ref HEAD
>
> Why don't you use a prompt?  Use the one in contrib/completion/git-prompt.sh.

While this is probably a good idea, not everybody has a prompt
configured. Imagine ssh'ing to a machine you haven't touched before,
or shouldn't configure. Sure, right now you need to configure it
anyway, but the whole proposal is to make these default aliases.

In Mercurial 'hg branch' shows only the current branch, and I think
that's more appropriate.

Before I configured my prompt, 'git branch' was by far the command I
used the most.

-- 
Felipe Contreras