git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git <git@vger.kernel.org>
Subject: Re: nd/setup
Date: Sat, 3 Apr 2010 16:39:05 +0200	[thread overview]
Message-ID: <z2gfcaeb9bf1004030739q9575b629p44c4461e90c37d40@mail.gmail.com> (raw)
In-Reply-To: <20100403050057.GA20525@progeny.tock>

On Sat, Apr 3, 2010 at 7:00 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Nguyen Thai Ngoc Duy wrote:
>
>> I haven't forgotten the "git init" with alias bug Jonathan found. Just
>> a little busy with other stuff.
>
> You already fixed it, I think. ;-)

Hmm.. so I do forget something. I still miss some of your good tests though.

> -- %< --
> Subject: Revert "help: use RUN_SETUP_GENTLY"
>
> Commit 717b8850580ecb9009505f71ea43ecda51ac1f0e taught ‘git help’
> to unconditionally looks for a git directory, with the justification:
>
>    So the sooner we set up gitdir, the less trouble we may have to
>    deal with.
>
> In the case of ‘git help -a’, that is not quite true.  In automount
> setups like that which prompted v1.6.0-rc0~121^2~1 (Add support for
> GIT_CEILING_DIRECTORIES, 2008-05-19), if GIT_CEILING_DIRECTORIES is
> unset, then probing for the Git directory can take a long time.  Thus
> unnecessarily searching for a git directory can slow down ‘git help -a’
> (and thus bash completion).
>
> ‘git help’ does not use RUN_SETUP or USE_PAGER, and neither option
> parsing nor producing output for plain ‘git help’ or ‘git help -a’
> requires access to the git configuration.  Therefore it is safe to not
> search for the git directory early in this case.
>
> Also add some comments to document the requirements this places on
> list_commands() and list_common_cmds_help().
>
> Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>

Didn't notice it. Looks good. I will replace the "help: use
RUN_SETUP_GENTLY" commit with this patch next time, if you don't mind.
-- 
Duy

  reply	other threads:[~2010-04-03 14:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-02  8:40 What's cooking in git.git (Apr 2010, #01; Fri, 02) Junio C Hamano
2010-04-02 11:23 ` Nguyen Thai Ngoc Duy
2010-04-03  5:00   ` nd/setup Jonathan Nieder
2010-04-03 14:39     ` Nguyen Thai Ngoc Duy [this message]
2010-04-04 18:41     ` nd/setup Nguyen Thai Ngoc Duy
2010-04-04 21:42       ` nd/setup Junio C Hamano
2010-04-02 16:48 ` What's cooking in git.git (Apr 2010, #01; Fri, 02) Sverre Rabbelier
2010-04-03  4:58 ` Nicolas Pitre
  -- strict thread matches above, loose matches on Subject: below --
2010-04-08  0:48 What's cooking in git.git (Apr 2010, #03; Wed, 07) Junio C Hamano
2010-04-08  7:38 ` Jeff King
2010-04-08 21:42   ` nd/setup Jonathan Nieder
2010-04-09  0:13     ` nd/setup Jeff King
2010-04-09  5:46     ` nd/setup Nguyen Thai Ngoc Duy
2010-04-09  5:57       ` nd/setup Jonathan Nieder
2010-04-09  6:56         ` nd/setup Nguyen Thai Ngoc Duy
2010-04-11 17:57     ` nd/setup Nguyen Thai Ngoc Duy

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=z2gfcaeb9bf1004030739q9575b629p44c4461e90c37d40@mail.gmail.com \
    --to=pclouds@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@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).