unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Philip Kaludercic <philipk@posteo.net>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Reviewing versioned backups
Date: Sun, 28 Mar 2021 11:23:36 +0200	[thread overview]
Message-ID: <87h7kvocmf.fsf@posteo.net> (raw)
In-Reply-To: <87y2e8t8nh.fsf@web.de> (Michael Heerdegen's message of "Sun, 28 Mar 2021 01:38:10 +0100")

Michael Heerdegen <michael_heerdegen@web.de> writes:

> Philip Kaludercic <philipk@posteo.net> writes:
>
>> I have been using version-control for years now, but have always
>> wondered if there was a better way to review previous versions besides
>> just going into your backup directory and manually comparing them. Is
>> there maybe a vc backend that uses the backup information? Or has
>> someone written some code to make it easier that they would care to
>> share?
>
> Magit has the "wip" modes that do more or less exactly that if your VCS
> is Git.  Once set up, backups are created automatically before and/or
> after each save (or at will).  They are saved in a chain of commits
> under a special reference name derived from your current branch's name.
>
> Big advantage: Git handles backups and you can do all the cool things
> like adding tags and annotations; Git can use delta compression to avoid
> wasting disk space, and all of this stuff.  One disadvantage currently:
> When you accidentally wip-commit something you didn't want to (e.g. a
> very large file or something containing passwords), you currently need
> to repair that accident using lowest-level git commands unless you can
> live with resetting the whole history to a prior state.  But apart from
> that, it works conveniently, there are log commands for your wip commits
> and such things etc.

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. But thank
you for the pointer, it might come in handy at some point in time!

-- 
	Philip K.



  reply	other threads:[~2021-03-28  9:23 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 [this message]
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
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=87h7kvocmf.fsf@posteo.net \
    --to=philipk@posteo.net \
    --cc=help-gnu-emacs@gnu.org \
    --cc=michael_heerdegen@web.de \
    /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).