From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/4] attr: notice and report read failure of .gitattributes files
Date: Thu, 20 Jun 2024 09:20:39 -0700 [thread overview]
Message-ID: <xmqqjzijy4a0.fsf@gitster.g> (raw)
In-Reply-To: <20240619135754.GB943023@coredump.intra.peff.net> (Jeff King's message of "Wed, 19 Jun 2024 09:57:54 -0400")
Jeff King <peff@peff.net> writes:
> I don't know that this is really consistent with callers of fopen(),
> since they tend to complain noisily. Usually via warn_on_fopen_errors(),
> which we ourselves call above.
Argh, you're right. I thought the guard in warn_on_fopen_errors()
would catch the artificial error code we give when we found that we
opened a directory (by mistake), but the error we use is EISDIR, so
it will be shown.
OK, let's scrap the whole thing. It does not look like it is
solving any real-world problems.
Thanks.
next prev parent reply other threads:[~2024-06-20 16:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-14 12:03 Non-blob .gitmodules and .gitattributes Alexey Pelykh
2024-06-14 15:35 ` Junio C Hamano
2024-06-14 15:43 ` Alexey Pelykh
2024-06-18 18:31 ` Jeff King
2024-06-18 19:07 ` Alexey Pelykh
2024-06-18 20:14 ` Junio C Hamano
2024-06-18 23:33 ` Jeff King
2024-06-18 23:44 ` [PATCH 0/4] .git{ignore,attributes} directories? Junio C Hamano
2024-06-18 23:44 ` [PATCH 1/4] .gitignore: introduce GITIGNORE_FILE CPP macro Junio C Hamano
2024-06-18 23:44 ` [PATCH 2/4] attr: notice and report read failure of .gitattributes files Junio C Hamano
2024-06-19 0:21 ` Eric Sunshine
2024-06-19 1:18 ` Junio C Hamano
2024-06-19 2:35 ` Eric Sunshine
2024-06-19 13:57 ` Jeff King
2024-06-20 16:20 ` Junio C Hamano [this message]
2024-06-18 23:44 ` [PATCH 3/4] exclude: notice and report read failure of .gitignore files Junio C Hamano
2024-06-18 23:44 ` [PATCH 4/4] submodule: ignore .gitmodules that is not a regular file Junio C Hamano
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=xmqqjzijy4a0.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--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.