git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: What's cooking in git.git (Mar 2010, #06; Wed, 24)

From
Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date
Mar 25, 2010, 15:16 UTC
Message-ID
<fcaeb9bf1003250816r16b06b1es6030b4fb8ae0a6de@mail.gmail.com>
In-Reply-To
<7v7hp1kzbn.fsf@alter.siamese.dyndns.org>
2010/3/25 Junio C Hamano <gitster@pobox.com>:
Show 43 quoted lines
> * 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
Previous: Nguyen Thai Ngoc DuyNext: Ben Walton
Message 8 of 13 in “What's cooking in git.git (Mar 2010, #06; Wed, 24)”
  1. Junio C HamanoMar 25, 2010
  2. Nguyen Thai Ngoc DuyMar 25, 2010
  3. Brandon CaseyMar 25, 2010
  4. Alex RiesenMar 25, 2010
  5. 1/2 Allow passing of configuration parameters in the command lineAlex Riesen, Mar 26, 2010
  6. 2/2 Use strbufs instead of open-coded string manipulationAlex Riesen, Mar 26, 2010
  7. Nguyen Thai Ngoc DuyMar 26, 2010
  8. Nguyen Thai Ngoc DuyMar 25, 2010
  9. Ben WaltonMar 26, 2010
  10. RPM spec: include bash completion supportIan Ward Comfort, Mar 26, 2010
  11. Ben WaltonMar 26, 2010
  12. Junio C HamanoMar 29, 2010
  13. Julian PhillipsMar 26, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.