From: Jean Louis <bugs@gnu.support>
To: Philip Kaludercic <philipk@posteo.net>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, help-gnu-emacs@gnu.org
Subject: Re: Reviewing versioned backups
Date: Tue, 30 Mar 2021 13:16:43 +0300 [thread overview]
Message-ID: <YGL6iwMqI6EaiSc2@protected.localdomain> (raw)
In-Reply-To: <87r1jxuh0f.fsf@posteo.net>
* Philip Kaludercic <philipk@posteo.net> [2021-03-30 12:29]:
> Michael Heerdegen <michael_heerdegen@web.de> writes:
>
> > Philip Kaludercic <philipk@posteo.net> writes:
> >
> >> This is interesting, but doesn't ~git~ fit my use-case, as I don't
> >> always use Git as my VCS and I use a lot of unversioned files.
> >
> > You could still use Git/Magit it but it would need some setup. You
> > could, for example, instruct `backup-directory-alist' to assign backups
> > a special directory, make it a Git repository, and instruct Emacs to
> > commit each new backup automatically.
>
> But this wouldn't give me a direct overview of all backup versions, it
> would just version the backups. What I am looking for is making use of
> versioned backups, that can easily be reviewed. I was wondering for the
> longest time why there is no interface for versioned backups.
Since you mentioned it, I had similar problem, but already had
database based backup system for database entries. Now I have extended
it that I can backup files, buffers and database entries in a single
database table. It is work in progress, not yet ready for public due
to few other files missing. But it can be done when I have time.
Emacs: RCD Version Control system with PostgreSQL backend
https://hyperscope.link/3/6/7/9/6/Emacs-RCD-Version-Control-system-with-PostgreSQL-backend-36796.html
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
next prev parent reply other threads:[~2021-03-30 10:16 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 19:21 Reviewing versioned backups Philip Kaludercic
2021-03-22 20:25 ` Jean Louis
2021-03-23 8:38 ` Eric S Fraga
2021-03-23 9:31 ` Jean Louis
2021-03-23 9:44 ` Eli Zaretskii
2021-03-23 10:19 ` Jean Louis
2021-03-23 11:12 ` Eli Zaretskii
2021-03-23 15:49 ` [External] : " Drew Adams
2021-03-23 9:56 ` Thibaut Verron
2021-03-23 11:55 ` Philip Kaludercic
2021-03-23 12:36 ` John Yates
2021-03-23 12:38 ` Eli Zaretskii
2021-03-24 8:47 ` Jean Louis
2021-03-24 11:05 ` Jean Louis
2021-03-24 16:53 ` Eli Zaretskii
2021-03-26 5:50 ` Robert Thorpe
2021-03-28 0:38 ` Michael Heerdegen
2021-03-28 9:23 ` Philip Kaludercic
2021-03-30 0:36 ` Michael Heerdegen
2021-03-30 9:29 ` Philip Kaludercic
2021-03-30 9:39 ` Eli Zaretskii
2021-03-30 10:03 ` Philip Kaludercic
2021-03-30 10:16 ` Jean Louis [this message]
2021-03-30 23:41 ` Michael Heerdegen
2021-03-31 1:56 ` Stefan Monnier
2021-03-31 6:24 ` Eli Zaretskii
2021-03-31 13:29 ` Philip Kaludercic
2021-03-31 14:00 ` Jean Louis
2021-04-01 15:52 ` Stefan Monnier
2021-04-01 19:44 ` Philip Kaludercic
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YGL6iwMqI6EaiSc2@protected.localdomain \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.de \
--cc=philipk@posteo.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).