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 16:01:37 +0200	[thread overview]
Message-ID: <8763ube27y.fsf@physik.rwth-aachen.de> (raw)
In-Reply-To: 85hcdvqqd1.fsf@lola.goethe.zz

Hallöchen!

David Kastrup writes:

> Torsten Bronger <bronger@physik.rwth-aachen.de> writes:
>
>> David Kastrup writes:
>>
>>> Torsten Bronger <bronger@physik.rwth-aachen.de> writes:
>>>
>>>> David Kastrup writes:
>>>>
>>>>> [...]  This decision has been made at a time where we were
>>>>> talking pretty much only about centralized versioning control
>>>>> systems, and the existence of distributed versioning control
>>>>> tips the scale even further, since local branches provide much
>>>>> better control over versioning and consistent state savings
>>>>> than backup files.
>>>>
>>>> Note however that the distributed VCS'es don't store local
>>>> copies of the last revision as CVS and SVN do.
>>>
>>> Huh?  Most certainly I can check out the last revision any time
>>> from my local version control system.
>>
>> I mean files like "thesis.tex.~1.3.~" in the same directory as your
>> working copies.
>
> I think you are confused.  Those aren't created by the version
> control system.  They are auxiliary files Emacs creates (or has
> the version control system create) for its own operation when it
> can't perform them otherwise.

Okay, sorry to have misled you.  But actually their origin doesn't
matter for what I tried to get across.  The typical cluttering up
that they generate in SVN working copies, and which may justify
avoiding additional eyesore by backup files, doesn't occur in
DVCS'es.

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 14:01 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
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 [this message]
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=8763ube27y.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).