From: Stuart Morrow <morrow.stuart@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Questions/concerns on gefs
Date: Thu, 15 Aug 2024 10:42:01 +0100 [thread overview]
Message-ID: <CABB-WO8TjaaFpyj1+sy13OdAAnZ0DSmMgvBrrRy6FwJDRmB3tQ@mail.gmail.com> (raw)
In-Reply-To: <D3GD55L8A4BL.U0P76UH03ZQE@trbsw.dev>
On Thu, 15 Aug 2024 at 10:04, Timothy Robert Bednarzyk <mail@trbsw.dev> wrote:
> some way to migrate from an fs(3) setup to a gefs-native setup? If not,
If nothing else you could copy it all with delorean (cinap's contrib)
and replica/cphist (quanstro's contrib). But it's pretty impossible
for that to be an in-place upgrade.
next prev parent reply other threads:[~2024-08-15 9:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-15 9:04 Timothy Robert Bednarzyk
2024-08-15 9:21 ` Steve Simon
2024-08-15 9:42 ` Stuart Morrow [this message]
2024-08-15 14:22 ` ori
2024-08-15 14:47 ` ori
2024-08-26 4:45 ` James Cook
2024-08-26 7:43 ` Steve Simon
2024-08-26 8:10 ` Frank D. Engel, Jr.
2024-08-26 8:26 ` Alex Musolino
2024-08-26 14:36 ` ron minnich
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-WO8TjaaFpyj1+sy13OdAAnZ0DSmMgvBrrRy6FwJDRmB3tQ@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).