unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
Cc: Stefan Monnier <monnier+gnu/emacs@rum.cs.yale.edu>
Subject: Re: [Fwd: [arch-users] Re: Gud lord!]
Date: Tue, 10 Jun 2003 16:16:17 -0400	[thread overview]
Message-ID: <20030610201617.GA26760@gnu.org> (raw)
In-Reply-To: <20030610165211.911A.JMBARRANQUERO@laley.wke.es>

On Tue, Jun 10, 2003 at 04:55:44PM +0200, Juanma Barranquero wrote:
> > It is a problem because you can't look inside with the usual tools,
> > so you end up locked with a specific set of tools and you have to
> > use them to get anything done.
> 
> Yes, but that's ameliorated if the format is well documented.

Well, no it's not.  If writing tools to get at the data is hard or risky then
things still suck, no matter how well documented the format is.

For many users, of course, it's the same either way, but one of the big
attractions of CVS was exactly that what it does is quite understandable, and
when all else failed, you could use emacs to edit the repository...

> > And when there's a bug, it can end up pretty disastrous (basically, the
> > big-binary-blob implements something like a file-system, so a bug is like
> > a bug in your kernel that can trash your entire file system).
> 
> Sure. Backups are always needed.

Um, that's not exactly a comforting answer...

I'd rather have things _not get trashed_!

Failing that, I'd like the damage to be limited, and recoverable, and the
more I can do this without using special tools, the better (special tools are
great when they work of course, but ...).

-Miles
-- 
`There are more things in heaven and earth, Horatio,
 Than are dreamt of in your philosophy.'

  parent reply	other threads:[~2003-06-10 20:16 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-08  1:09 [Fwd: [arch-users] Re: Gud lord!] Robert Anderson
2003-06-08  3:05 ` Alan Shutko
2003-06-08  5:01   ` Robert Anderson
2003-06-08 15:54     ` Stefan Monnier
2003-06-08 17:26       ` Robert Anderson
2003-06-09  8:23     ` Juanma Barranquero
2003-06-09 14:37       ` Robert Anderson
2003-06-09 15:00         ` Juanma Barranquero
2003-06-09 15:20           ` Miles Bader
2003-06-09 19:21           ` Jonathan Walther
2003-06-09 19:58             ` Stefan Monnier
     [not found]             ` <20030609214121.77EE.LEKTU@terra.es>
2003-06-09 20:11               ` Jonathan Walther
2003-06-10  7:14                 ` Juanma Barranquero
2003-06-10 12:59                   ` Miles Bader
2003-06-10 14:05                     ` Juanma Barranquero
2003-06-10 14:37                       ` Stefan Monnier
2003-06-10 14:55                         ` Juanma Barranquero
2003-06-10 15:03                           ` Stefan Monnier
2003-06-11  6:59                             ` Juanma Barranquero
2003-06-11 14:11                               ` Stefan Monnier
2003-06-11 14:40                                 ` Juanma Barranquero
2003-06-10 20:16                           ` Miles Bader [this message]
2003-06-11  7:10                             ` Juanma Barranquero
2003-06-10 14:54                       ` Robert Anderson
2003-06-11  0:25                   ` Richard Stallman
2003-06-11  7:19                     ` Juanma Barranquero
2003-06-11  9:54                       ` Jonathan Walther
2003-06-10  1:22           ` Robert Anderson
2003-06-10  6:53             ` Juanma Barranquero
2003-06-10 14:16               ` Robert Anderson
2003-06-08 15:51   ` Stefan Monnier
2003-06-09  1:18   ` Jonathan Walther
2003-06-09  1:47     ` Alan Shutko
2003-06-09  2:03       ` Jonathan Walther
2003-06-09 14:53       ` Robert Anderson
2003-06-09 15:20         ` Kai Großjohann
2003-06-10  0:35           ` Alex Schroeder
2003-06-10  6:12             ` Kai Großjohann

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=20030610201617.GA26760@gnu.org \
    --to=miles@gnu.org \
    --cc=monnier+gnu/emacs@rum.cs.yale.edu \
    /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).