From: Samuel Wales <samologist@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: is this data corruption?
Date: Sat, 31 Dec 2022 21:48:51 -0700 [thread overview]
Message-ID: <CAJcAo8sBT26BNg4j9EPCqwxpFF36QVMEqQnUDhqXQ3UH3AOPjA@mail.gmail.com> (raw)
In-Reply-To: <CAJcAo8sJo8mE5V8_3eGj3miirNOJfQGsDH+=7HmSrwvLC=Ch3w@mail.gmail.com>
of course i am still hoping, if possible,for generic adice on
repairing a repo, detecting a bug, whether it is a bug, what looks
curiously strange, maybe some more questions like the previous one
about what does --cached say, what does --histogram and --patience do,
etc., any of this whether or not a repro is possible. will repro if
possible just seems impossible.
On 12/31/22, Samuel Wales <samologist@gmail.com> wrote:
> hi,
>
> thanks for reading/thinking.
>
>> Sorry, but I do not see any "-" versions in the above. Simple and
> minimum reproduction recipe would be useful for the list to help.
>
> the - versions are identical. as i wrote, there are 2 - versions in
> addition. i didn't want to make a pointlessly long email.
>
> it would be great if i could provide a reproduction recipe. i don't
> know how i couold do that in this case. for example, when i try to
> pare down the repo and make private things obscured, i run into the
> proble that when i do staging, things change around, thus erasing that
> particular bug. and other stuff like my limited knowledge of git.
>
> i'm afraid i am stuck with hoping for other types of solutions like
> "i've seen this before" or "that's not possuble unless..."or something
> a priori like that. but if you have an idea of how to create a
> minimal repro in less than a week, let me know.
>
>
> On 12/31/22, Junio C Hamano <gitster@pobox.com> wrote:
>> Samuel Wales <samologist@gmail.com> writes:
>>
>>> the problem that seems like data corruption is that a few lines appear
>>> twice as - and once as +. but in the current version of the files,
>>> those lines exist only once. here are the lines. there are 2 -
>>> versions and one + version:
>>>
>>> +***************** REF bigpart is a partition
>>> +biglike and homelike are distracting nonsense i think except
>>> +to describe inferior filesets. anomalous subset of home
>>> +might be called homelike or so.
>>
>> Sorry, but I do not see any "-" versions in the above. Simple and
>> minimum reproduction recipe would be useful for the list to help.
>>
>> https://www.chiark.greenend.org.uk/~sgtatham/bugs.html
>>
>> Thanks.
>>
>
>
> --
> The Kafka Pandemic
>
> A blog about science, health, human rights, and misopathy:
> https://thekafkapandemic.blogspot.com
>
--
The Kafka Pandemic
A blog about science, health, human rights, and misopathy:
https://thekafkapandemic.blogspot.com
prev parent reply other threads:[~2023-01-01 4:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-31 0:17 is this data corruption? Samuel Wales
2022-12-31 0:25 ` rsbecker
2022-12-31 0:57 ` Samuel Wales
2023-01-01 1:15 ` Samuel Wales
2023-01-01 1:14 ` Samuel Wales
2022-12-31 0:33 ` Samuel Wales
2023-01-01 4:07 ` Junio C Hamano
2023-01-01 4:46 ` Samuel Wales
2023-01-01 4:48 ` Samuel Wales [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJcAo8sBT26BNg4j9EPCqwxpFF36QVMEqQnUDhqXQ3UH3AOPjA@mail.gmail.com \
--to=samologist@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).