From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Cc: Rolf Eike Beer <eb@emlix.com>
Subject: Re: data loss when doing ls-remote and piped to command
Date: Wed, 15 Sep 2021 11:17:42 -0700 [thread overview]
Message-ID: <xmqqwnnhwvnd.fsf@gitster.g> (raw)
In-Reply-To: <6786526.72e2EbofS7@devpool47> (Rolf Eike Beer's message of "Wed, 15 Sep 2021 14:43:10 +0200")
Rolf Eike Beer <eb@emlix.com> writes:
> The given repository is a clone of the vanilla kernel.
>
> /usr/bin/git --git-dir=/home/ebeer/repos/upstream/linux/.git ls-remote origin 2>&1 | less
>
> And I then see things like this:
>
> 6f38b5d6cfd43dde3058a10c68baae9cf17af912 refs/tags/v5.0-rc2
> 1c7fc5cbc33980acd13ae83d0b416db002fe95601e7f97f64b59514d936 refs/tags/v5.7-rc2^{}
> d0709bb6da2ab6d49b11643e98abdf79b1a2817f refs/tags/v5.7-rc3
Not offering any solution, just an observation of the problem and
annotating the report.
What we see on the second line is the beginning of peeled
v5.0-rc2^{} up to the "acd13" (that is, the first 19 bytes of the
line), followed by the full line for peeled v5.7-rc2^{} (which
begins with "ae83d"). 12407 bytes in between are missing, which
is even more puzzling as it is not a nice round number.
I wonder if this is "less" misconfigured and misbehaving. Did the
user after seeing v5.7-* tags scroll back with 'b' or something?
If the output (including the 2>&1 redirection) is sent to a file and
then "cat <that-file" is invoked, does the same thing happen? How
about "cat <that-file | less"?
next prev parent reply other threads:[~2021-09-15 18:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-15 12:43 data loss when doing ls-remote and piped to command Rolf Eike Beer
2021-09-15 18:17 ` Junio C Hamano [this message]
2021-09-16 6:38 ` Rolf Eike Beer
2021-09-16 10:12 ` Tobias Ulmer
2021-09-16 12:17 ` Rolf Eike Beer
2021-09-16 15:49 ` Mike Galbraith
2021-09-17 6:38 ` Mike Galbraith
2021-09-16 17:11 ` Linus Torvalds
2021-09-16 20:42 ` Junio C Hamano
2021-09-17 6:59 ` Rolf Eike Beer
2021-09-17 19:13 ` Jeff King
2021-09-17 19:28 ` Linus Torvalds
2021-09-18 6:33 ` Mike Galbraith
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=xmqqwnnhwvnd.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=eb@emlix.com \
--cc=git@vger.kernel.org \
/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).