From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: git SHA-256, perl 5.12, FUSE...
Date: Fri, 5 Nov 2021 21:13:17 +0000 [thread overview]
Message-ID: <20211105211317.GA12959@dcvr> (raw)
All of these will probably be in the future of public-inbox;
but I think I'm going to goof off with these in a
yet-to-be-announced AGPL project, first...
A bit tired after the 1.7 cycle and need a short break that
doesn't involve TCP (yet). But I've already found+fixed several
things related to public-inbox while half-way working on
aforementioned project:
public-inbox.git
54bc9f163df41423 (git: fix numerous bugs in git_quote and git_unquote, 2021-05-09)
git.git
00bc8390d8cd764c (remote-curl: fix clone on sha256 repos, 2021-05-11)
next reply other threads:[~2021-11-05 21:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-05 21:13 Eric Wong [this message]
2022-02-13 10:22 ` git SHA-256, perl 5.12, FUSE Eric Wong
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: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20211105211317.GA12959@dcvr \
--to=e@80x24.org \
--cc=meta@public-inbox.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 read-only IMAP folder(s) and NNTP newsgroup(s).