unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Torsten Bronger <bronger@physik.rwth-aachen.de>
To: emacs-devel@gnu.org
Subject: Re: backup files for files under VC
Date: Mon, 21 Apr 2008 14:18:35 +0200	[thread overview]
Message-ID: <87r6cze6zo.fsf@physik.rwth-aachen.de> (raw)
In-Reply-To: 85wsmrqv1j.fsf@lola.goethe.zz

Hallöchen!

David Kastrup writes:

> Torsten Bronger <bronger@physik.rwth-aachen.de> writes:
>
>> [...]
>>
>> If I change the file, save it, and remove it afterwards, the
>> changes are lost.
>
> Why would you do that without checking this into a branch when you
> have serious work done on it?

You may do it accidentally.  Backups are a protection from hardware
failure as well as human errors.  I'm talking about the latter here.

> [...]
>
>> In contrast to that, a backup file stores the last save instead
>> of the last commit.  And because this may help in some cases, I
>> suggest to change the default value of vc-make-backup-files.
>
> I vote against it.  Version-controlled directories become messy
> pretty fast with backup files lying around.

People who find this messy may switch it off if they please.
However, I think that the default should be in faviour of safety.

Maybe my workflow is unusual -- I've never talked with other people
about it -- but I use C-x C-s much more often than C-x v v when
editing versioned files.  Therefore, I think it is also for these
files sensible to keep backups of the last save.

Tschö,
Torsten.

-- 
Torsten Bronger, aquisgrana, europa vetus
                                      Jabber ID: bronger@jabber.org
               (See http://ime.webhop.org for further contact info.)





  reply	other threads:[~2008-04-21 12:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-21  7:57 backup files for files under VC Torsten Bronger
2008-04-21  8:30 ` Nick Roberts
2008-04-21  9:39 ` David Kastrup
2008-04-21 11:14   ` Torsten Bronger
2008-04-21 11:58     ` David Kastrup
2008-04-21 12:18       ` Torsten Bronger [this message]
2008-04-21 12:35         ` David Kastrup
2008-04-21 12:50           ` Torsten Bronger
2008-04-21 13:09             ` David Kastrup
2008-04-21 13:18               ` Torsten Bronger
2008-04-21 13:39                 ` David Kastrup
2008-04-21 14:01                   ` Torsten Bronger
2008-04-21 17:20                   ` Messy VC checkouts (was: backup files for files under VC) Phil Hagelberg
2008-04-21 18:00                     ` Messy VC checkouts Stefan Monnier
2008-04-21 18:18                     ` Thien-Thi Nguyen
2008-04-21 19:48               ` backup files for files under VC Richard Stallman
2008-04-21 14:53             ` Stefan Monnier
2008-04-21 15:47               ` Torsten Bronger
2008-04-21 16:27                 ` David Kastrup
2008-04-21 16:35                   ` Torsten Bronger
2008-04-21 14:48       ` Stefan Monnier
2008-04-21 15:20         ` David Kastrup

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=87r6cze6zo.fsf@physik.rwth-aachen.de \
    --to=bronger@physik.rwth-aachen.de \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).