unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Eric S. Raymond" <esr@thyrsus.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs-devel Digest, Vol 52, Issue 61
Date: Sat, 7 Jun 2008 15:55:44 -0400	[thread overview]
Message-ID: <20080607195544.GE1420@thyrsus.com> (raw)
In-Reply-To: <uod6dmick.fsf@gnu.org>

Eli Zaretskii <eliz@gnu.org>:
> > Date: Sat, 7 Jun 2008 09:20:37 -0400
> > From: "Eric S. Raymond" <esr@thyrsus.com>
> > 
> > Whoever said expecting builds in CVS to work consistently was
> > "hopelessly unrealistic" is simply revealing that the Emacs system
> > is broken as designed.
> 
> This is free software: you are welcome to fix whatever you think is
> broken.

Yeah, like I wouldn't get flamed to fare-thee-well if I shot autotools
through the head and replaced it with something like scons -- which is
only part of what needs to happen.  What we have here is a mess compounded
of the limitations of CVS, Makefiles, and configure, with a semi-infinite
number of layers of historical cruft layered over all three.

The real problem here isn't technical, it's cultural.  This crew is way
too used to rusty, broken, archaic tools like CVS and the high hassle
costs that go with them.  Until that changes, fixing the mess will
be theoretically conceivable but politically impossible.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>




  reply	other threads:[~2008-06-07 19:55 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080607125159.8A74F9F05B4@grelber.thyrsus.com>
2008-06-07 13:20 ` Emacs-devel Digest, Vol 52, Issue 61 Eric S. Raymond
2008-06-07 14:14   ` Alan Mackenzie
2008-06-07 14:07     ` Juanma Barranquero
2008-06-07 15:24       ` Alan Mackenzie
2008-06-07 15:29         ` Juanma Barranquero
2008-06-07 16:46         ` Eli Zaretskii
2008-06-07 18:34           ` Alan Mackenzie
2008-06-07 19:39             ` Eric S. Raymond
2008-06-07 19:53             ` Glenn Morris
2008-06-07 20:10               ` Eric S. Raymond
2008-06-07 20:53                 ` Eli Zaretskii
2008-06-07 21:12                   ` Eric S. Raymond
2008-06-08  2:49                   ` Stefan Monnier
2008-06-07 21:26                 ` Alan Mackenzie
2008-06-07 21:13                   ` Eric S. Raymond
2008-06-08  8:21                 ` Richard M Stallman
2008-06-07 21:15               ` Alan Mackenzie
2008-06-07 19:37           ` Eric S. Raymond
2008-06-07 19:40             ` David Kastrup
2008-06-07 22:14             ` Nick Roberts
2008-06-07 22:42               ` joakim
2008-06-07 22:47               ` David Kastrup
2008-06-08  2:46             ` Stefan Monnier
2008-06-08  2:50               ` Miles Bader
2008-06-10 10:36             ` use git, not cvs Jim Meyering
2008-06-10 10:42               ` Juanma Barranquero
2008-06-10 11:00                 ` Jim Meyering
2008-06-10 11:02                   ` Juanma Barranquero
2008-06-10 11:08               ` Miles Bader
2008-06-10 11:16                 ` Juanma Barranquero
2008-06-10 11:27                   ` Miles Bader
2008-06-10 11:30                     ` Juanma Barranquero
2008-06-10 11:34                     ` Jim Meyering
2008-06-10 11:20                 ` Jim Meyering
2008-06-10 11:26                   ` Nick Roberts
2008-06-10 14:33                 ` Stefan Monnier
2008-06-07 19:35       ` Emacs-devel Digest, Vol 52, Issue 61 Eric S. Raymond
2008-06-07 14:20   ` Chong Yidong
2008-06-07 14:23   ` Miles Bader
2008-06-07 19:41     ` Eric S. Raymond
2008-06-07 20:28       ` Eli Zaretskii
2008-06-08  0:50     ` Stephen J. Turnbull
2008-06-08  0:42       ` David Kastrup
2008-06-07 14:26   ` Eli Zaretskii
2008-06-07 19:55     ` Eric S. Raymond [this message]
2008-06-07 20:52       ` Eli Zaretskii
2008-06-07 21:26         ` Eric S. Raymond
2008-06-07 22:52           ` Thomas Lord
2008-06-08  0:58             ` Stephen J. Turnbull

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=20080607195544.GE1420@thyrsus.com \
    --to=esr@thyrsus.com \
    --cc=eliz@gnu.org \
    --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).