From: Junio C Hamano <gitster@pobox.com>
To: Matheus Tavares <matheus.bernardino@usp.br>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/2] checkout-index: omit entries with no tempname from --temp output
Date: Tue, 09 Feb 2021 13:35:36 -0800 [thread overview]
Message-ID: <xmqqmtwczzyv.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <1275701345b7e198ec83ad4fdcc2dda6d9775ef3.1612812581.git.matheus.bernardino@usp.br> (Matheus Tavares's message of "Mon, 8 Feb 2021 16:36:32 -0300")
Matheus Tavares <matheus.bernardino@usp.br> writes:
> With --temp (or --stage=all, which implies --temp), checkout-index
> writes a list to stdout associating temporary file names to the entries'
> names. But if it fails to write an entry, and the failure happens before
> even assigning a temporary filename to that entry, we get an odd output
> line. This can be seen when trying to check out a symlink whose blob is
> missing:
>
> $ missing_blob=$(git hash-object --stdin </dev/null)
> $ git update-index --add --cacheinfo 120000,$missing_blob,foo
> $ git checkout-index --temp foo
> error: unable to read sha1 file of foo (e69de29bb2d1d6434b8b29ae775ad8c2e48c5391)
> foo
>
> The 'TAB foo' line is not much useful and it might break scripts that
> expect the 'tempname TAB foo' output. So let's omit such entries from
> the stdout list (but leaving the error message on stderr).
Makes quite a lot of sense.
> if (CHECKOUT_ALL == checkout_stage) {
> - for (i = 1; i < 4; i++) {
> - if (i > 1)
> - putchar(' ');
> - if (topath[i][0])
> - fputs(topath[i], stdout);
> - else
> - putchar('.');
> + for (i = 1; i < 4; i++)
> + if (topath[i][0]) {
> + have_tempname = 1;
> + break;
> + }
> +
> + if (have_tempname) {
> + for (i = 1; i < 4; i++) {
> + if (i > 1)
> + putchar(' ');
> + if (topath[i][0])
> + fputs(topath[i], stdout);
> + else
> + putchar('.');
> + }
> }
> - } else
> + } else if (topath[checkout_stage][0]) {
> + have_tempname = 1;
> fputs(topath[checkout_stage], stdout);
> + }
>
> - putchar('\t');
> - write_name_quoted_relative(name, prefix, stdout,
> - nul_term_line ? '\0' : '\n');
> + if (have_tempname) {
> + putchar('\t');
> + write_name_quoted_relative(name, prefix, stdout,
> + nul_term_line ? '\0' : '\n');
>
> - for (i = 0; i < 4; i++) {
> - topath[i][0] = 0;
> + for (i = 0; i < 4; i++) {
> + topath[i][0] = 0;
> + }
> }
Hmph, is topath[][] array used after this function gets called and
in what way? Whether have_tempname is true or not, wouldn't we want
to clear it?
Thanks.
next prev parent reply other threads:[~2021-02-09 22:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-08 19:36 [PATCH 0/2] checkout-index: some cleanups to --temp and --prefix outputs Matheus Tavares
2021-02-08 19:36 ` [PATCH 1/2] write_entry(): fix misuses of `path` in error messages Matheus Tavares
2021-02-09 21:27 ` Junio C Hamano
2021-02-09 23:59 ` Matheus Tavares Bernardino
2021-02-08 19:36 ` [PATCH 2/2] checkout-index: omit entries with no tempname from --temp output Matheus Tavares
2021-02-09 21:35 ` Junio C Hamano [this message]
2021-02-09 21:57 ` Matheus Tavares Bernardino
2021-02-10 1:07 ` Junio C Hamano
2021-02-15 18:24 ` [PATCH v2 0/2] checkout-index: some cleanups to --temp and --prefix outputs Matheus Tavares
2021-02-15 18:24 ` [PATCH v2 1/2] write_entry(): fix misuses of `path` in error messages Matheus Tavares
2021-02-16 2:26 ` Junio C Hamano
2021-02-15 18:24 ` [PATCH v2 2/2] checkout-index: omit entries with no tempname from --temp output Matheus Tavares
2021-02-16 14:06 ` [PATCH v3 0/2] checkout-index: some cleanups to --temp and --prefix outputs Matheus Tavares
2021-02-16 14:06 ` [PATCH v3 1/2] write_entry(): fix misuses of `path` in error messages Matheus Tavares
2021-02-16 14:06 ` [PATCH v3 2/2] checkout-index: omit entries with no tempname from --temp output Matheus Tavares
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=xmqqmtwczzyv.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=matheus.bernardino@usp.br \
/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).