All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Murphy <lists@colorremedies.com>
To: unlisted-recipients:; (no To-header on input)
Cc: Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: Get the diff from a file in two snapshots.
Date: Mon, 26 Jan 2015 14:14:30 -0700	[thread overview]
Message-ID: <CAJCQCtRyv+m0kxBL6LW=xZv=sUzf2to4R6xPsxy6CkihHmrV0A@mail.gmail.com> (raw)
In-Reply-To: <CANXojczR_jeVU0XNQGzatmDaaCv7CdWanis8NiSe2F75cuz_9g@mail.gmail.com>

On Mon, Jan 26, 2015 at 1:52 PM, Stef Bon <stefbon@gmail.com> wrote:
> Hi,
>
> I'm working on a service/program for Linux which takes care of
> managing backupping of folders and the snapshots of those.
>
> The user can assign forlders he/she want to be backupped (corect
> English?), and create a profile for this folder. This profile is about
> the files which will be taken into process, and which not.
>
> As tool to backup and manage the snapshots I use btrfs.
> Now in my construction I get a lot of situations like:
>
> /path/to/snapshots/201501261603/path/to/some/file
>
> is another version of the same file at:
>
> /path/to/snapshots/201501252252/path/to/some/file
>
> is there a way to get the difference between these two files by making
> use of btrfs?

Snapper has this functionality built into it. I'm not sure if it uses
diff or something else. But the Snapper GUI in yast2 on opensuse will
let you see what files have changed between snapshots, click on the
file and it shows a color coded diff.

https://github.com/openSUSE/snapper



-- 
Chris Murphy

  reply	other threads:[~2015-01-26 21:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-26 20:52 Get the diff from a file in two snapshots Stef Bon
2015-01-26 21:14 ` Chris Murphy [this message]
2015-01-26 23:43   ` Stef Bon
2015-01-28  3:46     ` Zygo Blaxell
2015-01-28 10:28       ` Stef Bon

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='CAJCQCtRyv+m0kxBL6LW=xZv=sUzf2to4R6xPsxy6CkihHmrV0A@mail.gmail.com' \
    --to=lists@colorremedies.com \
    --cc=linux-btrfs@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.