From: A Large Angry SCM <gitzilla@gmail.com>
To: Sverre Rabbelier <srabbelier@gmail.com>
Cc: Stephen Boyd <bebarino@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Kirill Smelkov <kirr@mns.spb.ru>,
"Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: ks/precompute-completion (was Re: What's cooking in git.git (Oct 2009, #04; Wed, 21))
Date: Thu, 22 Oct 2009 18:20:35 -0400 [thread overview]
Message-ID: <4AE0DAB3.1030103@gmail.com> (raw)
In-Reply-To: <fabb9a1e0910221011r957246dx3162cd675ff16800@mail.gmail.com>
Sverre Rabbelier wrote:
> Heya,
>
> On Thu, Oct 22, 2009 at 03:34, Stephen Boyd <bebarino@gmail.com> wrote:
>> Junio C Hamano wrote:
>>> * ks/precompute-completion (2009-10-05) 1 commit.
>>> (merged to 'next' on 2009-10-14 at adf722a)
>>> + Speedup bash completion loading
>>>
>>> Are people happy with this?
>> No. I now have rebase.sh, am.sh, etc. in my completion
>
> I would really like it if running 'make && make install' in git.git
> would also build the completion script, I don't want to have to
> remember to run 'cd contrib/completion && make' every time we get new
> completion options :P.
>
Please do not for completion on those that did not ask for it.
next prev parent reply other threads:[~2009-10-22 22:28 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-22 6:52 What's cooking in git.git (Oct 2009, #04; Wed, 21) Junio C Hamano
2009-10-22 8:34 ` ks/precompute-completion (was Re: What's cooking in git.git (Oct 2009, #04; Wed, 21)) Stephen Boyd
2009-10-22 17:11 ` Sverre Rabbelier
2009-10-22 18:56 ` Stephen Boyd
2009-10-22 22:20 ` A Large Angry SCM [this message]
[not found] ` <fabb9a1e0910221555k287b45ebwb15ac97851b845f9@mail.gmail.com>
[not found] ` <fabb9a1e0910221556s694a344ag8e5ae07c35351ee4@mail.gmail.com>
2009-10-22 23:05 ` A Large Angry SCM
2009-10-23 18:27 ` Sverre Rabbelier
2009-10-23 18:59 ` ks/precompute-completion Junio C Hamano
2009-10-23 19:16 ` ks/precompute-completion Sverre Rabbelier
2009-10-23 20:05 ` ks/precompute-completion Junio C Hamano
2009-10-23 20:09 ` ks/precompute-completion Sverre Rabbelier
2009-10-23 20:20 ` ks/precompute-completion Jakub Narebski
2009-10-23 20:22 ` ks/precompute-completion Sverre Rabbelier
2009-10-23 22:29 ` ks/precompute-completion A Large Angry SCM
2009-10-23 22:39 ` ks/precompute-completion Sverre Rabbelier
2009-10-22 23:07 ` ks/precompute-completion (was Re: What's cooking in git.git (Oct 2009, #04; Wed, 21)) Johannes Schindelin
2009-10-22 8:46 ` What's cooking in git.git (Oct 2009, #04; Wed, 21) Jakub Narebski
2009-10-22 11:15 ` Nguyen Thai Ngoc Duy
2009-10-22 15:31 ` skillzero
2009-10-22 21:42 ` Junio C Hamano
2009-10-22 19:01 ` Stephen Boyd
2009-10-24 6:45 ` Junio C Hamano
2009-10-23 11:25 ` [PATCH] add tests for git diff --submodule Jens Lehmann
2009-10-24 19:25 ` Junio C Hamano
2009-10-25 16:02 ` What's cooking in git.git (Oct 2009, #04; Wed, 21) Clemens Buchacher
2009-10-26 7:14 ` Junio C Hamano
2009-10-26 8:29 ` Clemens Buchacher
2009-10-26 9:01 ` Stephen Boyd
2009-10-26 10:07 ` Clemens Buchacher
2009-10-27 18:27 ` vl/git-gui topic Shawn O. Pearce
2009-10-28 7:17 ` Junio C Hamano
2009-10-27 18:37 ` jp/dirty-describe topic Shawn O. Pearce
2009-10-28 14:47 ` sp/smart-http topic Shawn O. Pearce
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=4AE0DAB3.1030103@gmail.com \
--to=gitzilla@gmail.com \
--cc=bebarino@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kirr@mns.spb.ru \
--cc=spearce@spearce.org \
--cc=srabbelier@gmail.com \
/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.