From: Juanma Barranquero <jmbarranquero@laley.wke.es>
Cc: Miles Bader <miles@gnu.org>
Subject: Re: [Fwd: [arch-users] Re: Gud lord!]
Date: Wed, 11 Jun 2003 08:59:13 +0200 [thread overview]
Message-ID: <20030611085212.51D3.JMBARRANQUERO@laley.wke.es> (raw)
In-Reply-To: <200306101503.h5AF3EH9032505@rum.cs.yale.edu>
On Tue, 10 Jun 2003 11:03:14 -0400
"Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> wrote:
> when something goes wrong, you don't need to learn
> much about the in-repository format because it's basically obvious,
> so you can fix things fairly easily with the usual tools.
> I.e. you get to reuse the knowledge you've acquired while using
> all those other unix tools.
I've got the feeling that CVSROOT/* and friends are "basically obvious"
only to people with some sort of Unix background. But as you know, CVS
can be (and is) used from other, "friendlier" environments by people to
whom all these files would be black magic.
> I also think it tends to be over-emphasized
> in all those tools where they use new terms and warn you "this
> is a whole new concept" whereas in the end it's just very much
> all the same: edit, update, merge, diff, commit.
Yeah, I agree with that. Still, some of them insist in things like
decentralization, etc. I've got nothing against a centralized repository,
on the contrary :)
> Sure things like tags and branches might work differently, but
> note that Subversion is radically different from CVS in this respect
> as well ;-)
Fair enough :)
Juanma
next prev parent reply other threads:[~2003-06-11 6:59 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 [this message]
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
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=20030611085212.51D3.JMBARRANQUERO@laley.wke.es \
--to=jmbarranquero@laley.wke.es \
--cc=miles@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).