From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: "Bráulio Bhavamitra" <brauliobo@gmail.com>,
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: Thu, 30 May 2013 01:30:17 +0530 [thread overview]
Message-ID: <CALkWK0=Sn2myT3QPCWJnoxKH4hm4s7MaB=UrPixP87MFSwKoug@mail.gmail.com> (raw)
In-Reply-To: <CAMP44s1VFxarV4Gp5KsxhFKJbmd033-DW8koe9P4XUZQcX4mrA@mail.gmail.com>
Felipe Contreras wrote:
> 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).
Um, git blame revert.c when in builtin/ works for me: what am I missing?
>>> 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?
... but why would I want to club a slow network operation with
something like log? Yeah, I use git log @{u}.. all the time.
>>> 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.
Yeah, I saw that thread and I think shipping "sane" defaults is a lost
cause. I really want to make pull more useable, but by making it more
configurable.
>>> 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)'.
RIght, but we shouldn't ship anything "pretty" for scripts, otherwise
it'll become hard to understand them.
>>> head = !git l -1
>>
>> What is git l again?
>
> 'git log', of course.
I use 'git show' all the time.
>>> 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.
Like I said earlier, I'm really not interested in sane defaults: I
don't think all of us can agree on one thing.
> 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.
Yeah, we're fixing 'git branch' (by making it more configurable): the
topic is in progress.
next prev parent reply other threads:[~2013-05-29 20:01 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
2013-05-29 19:50 ` Felipe Contreras
2013-05-29 20:00 ` Ramkumar Ramachandra [this message]
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='CALkWK0=Sn2myT3QPCWJnoxKH4hm4s7MaB=UrPixP87MFSwKoug@mail.gmail.com' \
--to=artagnon@gmail.com \
--cc=Matthieu.Moy@imag.fr \
--cc=brauliobo@gmail.com \
--cc=felipe.contreras@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).