git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2010, #06; Wed, 24)
Date: Thu, 25 Mar 2010 16:16:55 +0100	[thread overview]
Message-ID: <fcaeb9bf1003250816r16b06b1es6030b4fb8ae0a6de@mail.gmail.com> (raw)
In-Reply-To: <7v7hp1kzbn.fsf@alter.siamese.dyndns.org>

2010/3/25 Junio C Hamano <gitster@pobox.com>:
> * nd/setup (2010-03-21) 40 commits
>  - Guard unallowed access to repository when it's not set up
>  - alias: keep repository found while collecting aliases as long as possible
>  - Allow to undo setup_git_directory_gently() gracefully (and fix alias code)
>  - builtins: check for startup_info->help, print and exit early
>  - builtins: utilize startup_info->help where possible
>  - run_builtin(): save "-h" detection result for later use
>  - config: do not read .git/config if there is no repository
>  - apply: do not check sha1 when repository has not been found
>  - Do not read .git/info/attributes if there is no repository
>  - Do not read .git/info/exclude if there is no repository
>  - git_config(): do not read .git/config if there is no repository
>  - init/clone: turn on startup->have_repository properly
>  - worktree setup: restore original state when things go wrong
>  - Use git_config_early() instead of git_config() during repo setup
>  - Add git_config_early()
>  - worktree setup: call set_git_dir explicitly
>  - rev-parse --git-dir: print relative gitdir correctly
>  - enter_repo(): initialize other variables as setup_git_directory_gently() does
>  - Move enter_repo() to setup.c
>  - index-pack: use RUN_SETUP_GENTLY
>  - index-pack: trust the prefix returned by setup_git_directory_gently()
>  - worktree setup: calculate prefix even if no worktree is found
>  - merge-file: use RUN_SETUP_GENTLY
>  - var: use RUN_SETUP_GENTLY
>  - ls-remote: use RUN_SETUP_GENTLY
>  - help: use RUN_SETUP_GENTLY
>  - diff: use RUN_SETUP_GENTLY
>  - bundle: use RUN_SETUP_GENTLY
>  - apply: use RUN_SETUP_GENTLY
>  - verify-pack: use RUN_SETUP_GENTLY
>  - check-ref-format: use RUN_SETUP_GENTLY
>  - mailinfo: use RUN_SETUP_GENTLY
>  - archive: use RUN_SETUP_GENTLY
>  - builtin: USE_PAGER should not be used without RUN_SETUP*
>  - grep: use RUN_SETUP_GENTLY
>  - shortlog: use RUN_SETUP_GENTLY
>  - hash-object: use RUN_SETUP_GENTLY
>  - config: use RUN_SETUP_GENTLY
>  - builtin: Support RUN_SETUP_GENTLY to set up repository early if found
>  - builtin: introduce startup_info struct
>
> This seems to break t7006 when merged to 'pu'.

Unfortunately that test does not break on my machine (b745e293f).
t9100 breaks though. I´m looking into it.

Can you send me ¨./t7006-* -v¨ output? If you have free time
(unlikely), and the output says ¨internal error: access to .git/config
without repo setup¨ or ¨internal error: setup_git_env can´t be called
twice¨, can you run gdb and give me the stack trace when it die()? I
could have missed some code path.
-- 
Duy

  parent reply	other threads:[~2010-03-25 15:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25  0:41 What's cooking in git.git (Mar 2010, #06; Wed, 24) Junio C Hamano
2010-03-25 15:11 ` Nguyen Thai Ngoc Duy
2010-03-25 16:27   ` Brandon Casey
2010-03-25 23:11     ` Alex Riesen
2010-03-26 22:53       ` [PATCH 1/2] Allow passing of configuration parameters in the command line Alex Riesen
2010-03-26 22:56         ` [PATCH 2/2] Use strbufs instead of open-coded string manipulation Alex Riesen
2010-03-26  5:47     ` What's cooking in git.git (Mar 2010, #06; Wed, 24) Nguyen Thai Ngoc Duy
2010-03-25 15:16 ` Nguyen Thai Ngoc Duy [this message]
2010-03-26  2:19 ` Ben Walton
2010-03-26  8:39   ` [PATCH] RPM spec: include bash completion support Ian Ward Comfort
2010-03-26 12:10     ` Ben Walton
2010-03-29 18:17       ` Junio C Hamano
2010-03-26 13:07     ` Julian Phillips

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