All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Rosenfeld Rosas <lbocseg@yahoo.com.br>
To: "SZEDER Gábor" <szeder@fzi.de>
Cc: Jonathan Nieder <jrnieder@gmail.com>,
	Thomas Rast <trast@student.ethz.ch>,
	git@vger.kernel.org
Subject: Re: [PATCH/RFC] bash: add --word-diff option to diff [AND --set-upstream TO push] auto-completion
Date: Fri, 16 Sep 2011 12:56:09 -0300	[thread overview]
Message-ID: <4E737199.1000107@yahoo.com.br> (raw)
In-Reply-To: <20110913233712.GE2078@goldbirke>

While on the topic, it would also be interesting to add "--set-upstream" 
to "git push" autocompletion. Don't you agree?

Cheers, Rodrigo.

Em 13-09-2011 20:37, SZEDER Gábor escreveu:
> On Wed, Sep 14, 2011 at 01:29:41AM +0200, SZEDER Gábor wrote:
>> Or is it just too late here and I'm missing something
>> obvious?
>>
>> Completing the mode for --word-diff=<TAB>  is a good idea, but c'mon,
>> there are plenty of examples ;)  Have a look at _git_am(),
>> _git_format_patch(), or _git_init() for something easy, and
>> _git_commit(), _git_log(), or _git_notes() for something fancy.
>>
>> Note that --word-diff= is also valid for log and shortlog, so the same
>> can be done there, too.
>
> Not shortlog, show.  It's definitely too late... ;)
>
>

  reply	other threads:[~2011-09-16 16:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4E6F720A.3020103@yahoo.com.br>
     [not found] ` <20110913165847.GB11076@elie>
     [not found]   ` <4E6FA541.7000100@yahoo.com.br>
2011-09-13 19:14     ` [PATCH/RFC] bash: add --word-diff option to diff auto-completion Jonathan Nieder
2011-09-13 23:29       ` SZEDER Gábor
2011-09-13 23:37         ` SZEDER Gábor
2011-09-16 15:56           ` Rodrigo Rosenfeld Rosas [this message]
2011-09-16 20:47             ` [PATCH/RFC] bash: add --word-diff option to diff [AND --set-upstream TO push] auto-completion Jonathan Nieder

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

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

  git send-email \
    --in-reply-to=4E737199.1000107@yahoo.com.br \
    --to=lbocseg@yahoo.com.br \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@gmail.com \
    --cc=szeder@fzi.de \
    --cc=trast@student.ethz.ch \
    /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. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.