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

Re: What's cooking in git.git (Jun 2017, #01; Thu, 1)

From
Johannes Sixt <j6t@kdbg.org>
Date
Jun 1, 2017, 21:06 UTC
Message-ID
<ebe29db6-45ed-81d7-2a3e-24437406eb08@kdbg.org>
In-Reply-To
<xmqqshjk5ezb.fsf@gitster.mtv.corp.google.com>
Am 01.06.2017 um 09:44 schrieb Junio C Hamano:
Show 21 quoted lines
> * nd/fopen-errors (2017-05-30) 14 commits
>   - mingw_fopen: report ENOENT for invalid file names
>   - SQUASH??? use test_i18ngrep and add it at the end
>   - mingw: verify that paths are not mistaken for remote nicknames
>   - log: fix memory leak in open_next_file()
>   - rerere.c: move error_errno() closer to the source system call
>   - print errno when reporting a system call error
>   - wrapper.c: make warn_on_inaccessible() static
>   - wrapper.c: add and use fopen_or_warn()
>   - wrapper.c: add and use warn_on_fopen_errors()
>   - config.mak.uname: set FREAD_READS_DIRECTORIES for Darwin, too
>   - config.mak.uname: set FREAD_READS_DIRECTORIES for Linux and FreeBSD
>   - clone: use xfopen() instead of fopen()
>   - use xfopen() in more places
>   - git_fopen: fix a sparse 'not declared' warning
> 
>   We often try to open a file for reading whose existence is
>   optional, and silently ignore errors from open/fopen; report such
>   errors if they are not due to missing files.
> 
>   Waiting for an Ack to the SQUASH fix or a reroll of the tip commits.
ACK!

See also https://public-inbox.org/git/2899d715-a416-1852-4399-28af0a3e9b6e@kdbg.org/

-- Hannes
Previous: Johannes SchindelinNext: Junio C Hamano
Message 8 of 9 in “What's cooking in git.git (Jun 2017, #01; Thu, 1)”
  1. Junio C HamanoJun 1, 2017
  2. preserve untracked cache, was Re: What's cooking in git.git (Jun 2017, #01; Thu, 1)Johannes Schindelin, Jun 1, 2017
  3. Samuel LijinJun 1, 2017
  4. Junio C HamanoJun 1, 2017
  5. Johannes SchindelinJun 2, 2017
  6. Junio C HamanoJun 3, 2017
  7. Johannes SchindelinJun 15, 2017
  8. Johannes SixtJun 1, 2017
  9. Junio C HamanoJun 1, 2017

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.