Github messages for voidlinux
 help / color / mirror / Atom feed
From: foxlet <foxlet@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: ntfs2btrfs
Date: Fri, 15 Oct 2021 08:41:26 +0200	[thread overview]
Message-ID: <20211015064126.8urU0KoGpEv4C2XL5RvCnTXBsKORoYS7Qqx9FVQmPMA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-33396@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 835 bytes --]

New comment by foxlet on void-packages repository

https://github.com/void-linux/void-packages/pull/33396#issuecomment-944041420

Comment:
> https://github.com/maharmstone/ntfs2btrfs/issues there are still a few issues, and merging it into distro repos counts as endorsement, even if slight. How comfortable are you with the tool?

Many of those issues are related to the Windows version or have been superseded by newer versions (with the original issuer not coming back to the thread). There will always be a risk to data without a backup (as with any tool), but I've used both this and its sister project WinBtrfs in production systems with no noticeable issues. 

FS changes are also reversible as the original NTFS metadata is preserved inside of a snapshot within new btrfs filesystem, so there is additional recourse there.

  parent reply	other threads:[~2021-10-15  6:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-07  2:59 [PR PATCH] " foxlet
2021-10-07  3:17 ` [PR REVIEW] " ericonr
2021-10-07 22:45 ` [PR PATCH] [Updated] " foxlet
2021-10-08 14:45 ` ericonr
2021-10-15  6:41 ` foxlet [this message]
2021-10-24 16:14 ` [PR PATCH] [Merged]: " ericonr

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=20211015064126.8urU0KoGpEv4C2XL5RvCnTXBsKORoYS7Qqx9FVQmPMA@z \
    --to=foxlet@users.noreply.github.com \
    --cc=ml@inbox.vuxu.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).