From: Stuart Morrow <morrow.stuart@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Re: sysupdate: no common ancestors
Date: Tue, 27 Jul 2021 10:47:29 +0000 [thread overview]
Message-ID: <CABB-WO__ZbgRUXJw=Z2_4VmV5DaBoa-9MtqELPzkrbEM30iOUw@mail.gmail.com> (raw)
In-Reply-To: <86D72FF5B95E8137C8104389DA5DF1F5@eigenstate.org>
I applied that patch (yes, and did fetch.install, it's confirmed just
now by strings /bin/git/fetch) and reset the commit IDs.
I reset the commit IDs again and now sysupdate just says (straight
away, if that's a clue) up to date.
Of course this time my fetch is the one from "git/fetch: be more
robust" (confirmed by mtime).
next prev parent reply other threads:[~2021-07-27 10:50 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
2021-07-27 10:47 ` Stuart Morrow [this message]
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='CABB-WO__ZbgRUXJw=Z2_4VmV5DaBoa-9MtqELPzkrbEM30iOUw@mail.gmail.com' \
--to=morrow.stuart@gmail.com \
--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).