From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] Re: sysupdate: no common ancestors
Date: Mon, 26 Jul 2021 22:28:57 -0400 [thread overview]
Message-ID: <86D72FF5B95E8137C8104389DA5DF1F5@eigenstate.org> (raw)
In-Reply-To: <8EF9D0FDB7D0AF622272DFD20B9AE504@eigenstate.org>
Quoth ori@eigenstate.org:
> Quoth Anthony Martin <ality@pbrane.org>:
> > An update:
> >
> > Stuart sent me his pack and index files and,
> > fortunately, it looks like they're all valid
> > so far (I'm working backwards from the most
> > recent).
> >
> > However, two commits (c38fcb5dc and 2c1727e55)
> > are completely missing from any pack. I wonder
> > why git/fetch never asked the remote for those
> > refs or why they were never sent.
> >
> > Also, curiously, one commit (be36c092a) appears
> > in two packs.
> >
> > I'm going to keep thinking about this but my
> > current notes are appended below.
> >
> > Cheers,
> > Anthony
> >
>
> Hm. Is it possible that we had mistakenly
> updated the refs, and then pruned commits
> out of the request in subsequent updates?
>
Actually: did you run into the issue mentined in
the mail with subject 'ISO 9front-8591: AVOID'?
Did you go through the instructions for fixing the
references mentioned there?
(It's safe to repeat them)
next prev parent reply other threads:[~2021-07-27 9:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-25 20:12 [9front] " Stuart Morrow
2021-07-25 20:20 ` ori
2021-07-25 20:42 ` Stuart Morrow
2021-07-25 22:40 ` Anthony Martin
2021-07-26 15:58 ` [9front] " Anthony Martin
2021-07-26 17:34 ` Stuart Morrow
2021-07-27 0:07 ` Anthony Martin
2021-07-27 1:04 ` ori
2021-07-27 2:28 ` ori [this message]
2021-07-27 10:47 ` Stuart Morrow
2021-07-27 10:53 ` Stuart Morrow
2021-07-27 14:44 ` ori
2021-07-29 19:51 ` Stuart Morrow
2021-07-29 22:13 ` ori
2021-07-31 19:59 ` Stuart Morrow
2021-08-01 23:34 ` ori
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=86D72FF5B95E8137C8104389DA5DF1F5@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.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).