unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Garreau\, Alexandre" <galex-713@galex-713.eu>
To: Van L <van@scratch.space>
Cc: Help GNU Emacs <help-gnu-emacs@gnu.org>
Subject: Fossil [Was: Re: How to disable auto save on Emacs 26.1]
Date: Sat, 06 Oct 2018 13:34:17 +0200	[thread overview]
Message-ID: <r47dzyzzzzzz.wj8.xxuns.g6.gal_-_@portable.galex-713.eu> (raw)
In-Reply-To: <32B00B20-58FF-4E30-9B9F-42A4467CD2CA@scratch.space> (Van L.'s message of "Fri, 5 Oct 2018 00:47:54 +1000")

On 2018-10-05 at 00:47, Van L wrote:
>> Think of backup files (I
>> generally use numeric backups to actually retain more than one old
>> copy - more clutter!) as a defense against shooting yourself in the
>> foot. A version control system does that, only better. Tools like Git
>> or Mercurial make it trivial to create and manage little repositories
>> ("git init" creates a new repo in the current directory, for example).
>> You need not push changes to a central server if you don't care to.
>
> A complete beginner might want to try fossil.

Isn’t fossil (also?) Plan9’s versioned immutable file system?

> It has builtin wiki, ticket tracking, and web-frontend.

isn’t that even more cluttered if you don’t need that but only backups?



  reply	other threads:[~2018-10-06 11:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-03 13:10 How to disable auto save on Emacs 26.1 Tom Wallenfang
2018-10-03 13:34 ` Martin Šlouf
2018-10-03 13:55 ` Stefan Monnier
     [not found] ` <mailman.1669.1538575056.1284.help-gnu-emacs@gnu.org>
2018-10-03 14:16   ` Tom Wallenfang
2018-10-04 11:04     ` tomas
2018-10-04 12:55       ` Skip Montanaro
2018-10-04 14:47         ` Van L
2018-10-06 11:34           ` Garreau, Alexandre [this message]
2018-10-06 14:32             ` Fossil [Was: Re: How to disable auto save on Emacs 26.1] Van L
2018-10-06 19:17             ` tomas
2018-10-04 17:21         ` How to disable auto save on Emacs 26.1 Marcin Borkowski
2018-10-06  6:24           ` Marcin Borkowski
     [not found]       ` <mailman.1701.1538657386.1284.help-gnu-emacs@gnu.org>
2018-10-05 18:04         ` James K. Lowden
     [not found]     ` <mailman.1698.1538651613.1284.help-gnu-emacs@gnu.org>
2018-10-04 13:10       ` Stefan Monnier
2018-10-04 14:49         ` tomas
2018-10-04 13:44       ` Tom Wallenfang
     [not found] ` <mailman.1668.1538573687.1284.help-gnu-emacs@gnu.org>
2018-10-03 14:19   ` Tom Wallenfang

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=r47dzyzzzzzz.wj8.xxuns.g6.gal_-_@portable.galex-713.eu \
    --to=galex-713@galex-713.eu \
    --cc=help-gnu-emacs@gnu.org \
    --cc=van@scratch.space \
    /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).