From: Lars Brinkhoff <lars@nocrew.org>
To: Jan-Benedict Glaw <jbglaw@lug-owl.de>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: Extracting files from various old dump/restore tapes
Date: Thu, 15 Sep 2022 05:45:17 +0000 [thread overview]
Message-ID: <7wedwd42du.fsf@junk.nocrew.org> (raw)
In-Reply-To: <20220914213325.wqdkdocq6lajjubw@lug-owl.de> (Jan-Benedict Glaw's message of "Wed, 14 Sep 2022 23:33:25 +0200")
Jan-Benedict Glaw wrote:
> Here's some stuff to build it, at least on my side.
> * -Ilibword does not exist
> * Seems `classify-tape.c` got renamed to `classify.c`
> * read_32bits_l() is unused and produces a warning
Thanks! I fumbled some last-minute changes. And frankly, I didn't
expect anyone to pick it up so quickly!
prev parent reply other threads:[~2022-09-15 5:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-22 15:35 [TUHS] " Lars Brinkhoff
2022-08-22 16:27 ` [TUHS] " Warner Losh
2022-08-22 16:53 ` Bakul Shah
2022-08-22 16:56 ` Warner Losh
2022-08-23 5:55 ` Lars Brinkhoff
2022-08-23 13:02 ` Warner Losh
2022-09-09 5:51 ` Lars Brinkhoff
2022-09-14 17:48 ` Lars Brinkhoff
2022-09-14 21:33 ` Jan-Benedict Glaw
2022-09-15 5:45 ` Lars Brinkhoff [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7wedwd42du.fsf@junk.nocrew.org \
--to=lars@nocrew.org \
--cc=jbglaw@lug-owl.de \
--cc=tuhs@tuhs.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).