From: Alan Shutko <ats@acm.org>
Cc: emacs-devel@gnu.org
Subject: Re: [Fwd: [arch-users] Re: Gud lord!]
Date: Sun, 08 Jun 2003 20:47:19 -0500 [thread overview]
Message-ID: <87ptlo58ew.fsf@wesley.springies.com> (raw)
In-Reply-To: <20030609011846.GB19331@reactor-core.org> (Jonathan Walther's message of "Sun, 8 Jun 2003 18:18:46 -0700")
Jonathan Walther <krooger@debian.org> writes:
> I can't take the time to learn how to use that wheel-barrow, I have a
> foundation to dig; I'll just keep carrying the dirt over to the pile a
> shovelful at a time.
That's a very bad analogy, since CVS is currently working, you just
have pain when renaming files.
(Besides, it doesn't make sense. Does anyone dig foundations by hand?
If you are, your wheelbarrow is the least of your problems. Maybe you
could have an analogy with construction equipment, but if asked in the
middle of a task to switch and retrain on new equipment with a
completely different interface and design philosophy, most builders
would laugh at you.)
>>And since arch is immature
>
> Arch is usably mature, with multiple implementations in various
> languages.
How many years of experience has arch had? The implementation(s) may be
perfectly mature, but that doesn't mean that people's understanding of
it is.
If you'd like to see Emacs using arch, since arch is so decentralized,
maybe you or Robert could start maintaining an Emacs arch repository.
You could then figure out what the best setup for Emacs development
would be, which would make it much easier for an eventual wholesale
switch, since the rest of the developers could take advantage of your
knowledge.
--
Alan Shutko <ats@acm.org> - I am the rocks.
Looking for a developer in St. Louis? http://web.springies.com/~ats/
next prev parent reply other threads:[~2003-06-09 1:47 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
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 [this message]
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=87ptlo58ew.fsf@wesley.springies.com \
--to=ats@acm.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).