From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Sverre Rabbelier <srabbelier@gmail.com>,
gitzilla@gmail.com, git@vger.kernel.org,
"Shawn O. Pearce" <spearce@spearce.org>,
Kirill Smelkov <kirr@mns.spb.ru>,
Stephen Boyd <bebarino@gmail.com>
Subject: Re: ks/precompute-completion
Date: Fri, 23 Oct 2009 13:20:19 -0700 (PDT) [thread overview]
Message-ID: <m3d44deu93.fsf@localhost.localdomain> (raw)
In-Reply-To: <7v1vktc1uk.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster@pobox.com> writes:
> Sverre Rabbelier <srabbelier@gmail.com> writes:
>
> > This is my main concern, adding 'bash_completion' as a target to all:
> > would be ok; why would 'make clean' break it? As long as you don't add
> > "make -C contrib/completion clean' to the main clean target there's no
> > problem?
>
> "make clean" should remove it, because it is a normal build product,
> if you make your "make all" build completion scripts.
>
> The word _should_ is used in the RFC2119 sense: there may exist valid
> reasons in particular circumstances to ignore a particular item, but the
> full implications must be understood and carefully weighed before choosing
> a different course.
If we take similar approach to the way gitweb can be build to the bash
completion script, which means building it via
make contrib/completion/git-completion.bash
(and not make this target part of "make all"), then there is, I think,
no reason for "make clean" to remove it, isn't it?
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2009-10-23 20:25 UTC|newest]
Thread overview: 37+ 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
[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 ` Jakub Narebski [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2009-11-11 9:34 excerpts from tomorrow's "What's cooking" draft Junio C Hamano
2009-11-11 17:57 ` Sverre Rabbelier
2009-11-11 22:08 ` ks/precompute-completion Jonathan Nieder
2009-11-13 6:40 ` ks/precompute-completion Stephen Boyd
2009-11-13 7:06 ` ks/precompute-completion Jonathan Nieder
2009-11-13 7:12 ` ks/precompute-completion Stephen Boyd
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=m3d44deu93.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=bebarino@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=gitzilla@gmail.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 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 NNTP newsgroup(s).