[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Monotone-devel] Re: [ANNOUNCE] monotone 0.21 released
From: |
Ethan Blanton |
Subject: |
Re: [Monotone-devel] Re: [ANNOUNCE] monotone 0.21 released |
Date: |
Wed, 20 Jul 2005 23:06:15 -0500 |
User-agent: |
Mutt/1.4.1i |
Nathaniel Smith spake unto us the following wisdom:
> > That behavior forces you to specify all --excluded branches
> > on the command line every time you sync, and that's pretty
> > uncomfortable. (Default patterns don't help me when I have
> > to sync to different servers with different configurations.)
>
> Can you explain some more about your situation? Why do you have lots
> of servers? Why do they all have different --exclude patterns? Why
> are you pulling all them into the same db? Maybe there's some other
> change that would make you even happier :-)
I personally have used (and will use) monotone to sync to more than one
server from the same database, and even working directory; this is pre-
cisely the reason I want a distributed SCM. :-) Additonally, I have
placed all of my projects on the same server for the purpose of sharing,
simply because setting up one server and poking one hole in a firewall
and only having to remember one hostname instead of a set of host-
name:port pairs are all the path of least resistance. I foresee many
*users* following a similar path. Projects, of course, will set up
servers dedicated to one project.
In short, I see the "many different servers of many different configura-
tions" coming into play often when syncing side-branches with other
developers.
Ethan
--
The laws that forbid the carrying of arms are laws [that have no remedy
for evils]. They disarm only those who are neither inclined nor
determined to commit crimes.
-- Cesare Beccaria, "On Crimes and Punishments", 1764
pgpTqHxlr1oLY.pgp
Description: PGP signature