From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Jeff King" <peff@peff.net>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
git@vger.kernel.org
Subject: Re: [PATCH] Remove .git auto detection from setup_git_env()
Date: Fri, 05 Feb 2010 21:29:34 +0100 [thread overview]
Message-ID: <4B6C7FAE.5070104@lsrfire.ath.cx> (raw)
In-Reply-To: <7vljf7a901.fsf@alter.siamese.dyndns.org>
Am 05.02.2010 18:27, schrieb Junio C Hamano:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> This topic started from "We broke 'git grep' in .git directory" and I
>> think it is the sanest to revert 3081623 (grep --no-index: allow use of
>> "git grep" outside a git repository, 2010-01-15) which nobody has used so
>> far in any released version of git, until we sort this out at least.
>
> Sorry; spoke too fast. We'd also need to revert the one to git.c (7e62265
> (grep: prepare to run outside of a work tree, 2010-01-15) as well.
> { "fsck-objects", cmd_fsck, RUN_SETUP },
> { "gc", cmd_gc, RUN_SETUP },
> { "get-tar-commit-id", cmd_get_tar_commit_id },
> - { "grep", cmd_grep, USE_PAGER },
> + { "grep", cmd_grep, RUN_SETUP | USE_PAGER },
> { "hash-object", cmd_hash_object },
> { "help", cmd_help },
> { "index-pack", cmd_index_pack },
There is one other command with only the USE_PAGER flag turned on, which
also seems to have been broken by the change to remove the RUN_SETUP
flag: shortlog. But that was done in March 2008 (abe549e1, "shortlog:
do not require to run from inside a git repository"), so it's no regression.
René
prev parent reply other threads:[~2010-02-05 20:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 11:47 [PATCH] Remove .git auto detection from setup_git_env() Nguyễn Thái Ngọc Duy
2010-02-05 15:12 ` Jeff King
2010-02-05 17:22 ` Junio C Hamano
2010-02-05 17:27 ` Junio C Hamano
2010-02-05 20:29 ` René Scharfe [this message]
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=4B6C7FAE.5070104@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@gmail.com \
--cc=peff@peff.net \
/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.