public inbox for linux-bcachefs@vger.kernel.org
 help / color / mirror / Atom feed
From: Franz Schultz <franz.schultz@posteo.de>
To: Kent Overstreet <kent.overstreet@linux.dev>
Cc: linux-bcachefs@vger.kernel.org
Subject: Re: Version Control capabilities plus two small unrelated questions
Date: Tue, 30 Dec 2025 23:42:40 +0000	[thread overview]
Message-ID: <a22e9f3803d4c60f878f11366aaeda39@posteo.net> (raw)
In-Reply-To: <7dgvgc3usnl4nbpivj3wuemprknevx5tudji4ldzqkq7ngvfva@sbdg5tfhjnll>

I'm also interested in such version control design within the FS where 
you save the current version of a file and then are able to access the 
timeline of all such saved versions.

> In particular is there a standard way to 'follow' the same file along 
> its
> snapshotted versions? Say, ask bcachefs to return the list of 
> snapshotted
> versions by giving input this or that file in the current version of 
> the
> filesystem? Note that if such file was deleted and another with the 
> same
> name created I don't want that new file also to show up. And related
> question, is there any command that would list the snapshotted files 
> which
> have no corresponding in the current version of the file system (for 
> example
> because I deleted such file after having snapshotted it)?


      parent reply	other threads:[~2025-12-30 23:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-24 16:02 Version Control capabilities plus two small unrelated questions BP25
2025-12-24 16:11 ` BP25
2025-12-26 17:09 ` Kent Overstreet
2025-12-27  0:08   ` BP25
2025-12-30 23:42   ` Franz Schultz [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=a22e9f3803d4c60f878f11366aaeda39@posteo.net \
    --to=franz.schultz@posteo.de \
    --cc=kent.overstreet@linux.dev \
    --cc=linux-bcachefs@vger.kernel.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