[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: |
Richard Levitte - VMS Whacker |
Subject: |
Re: [Monotone-devel] Re: [ANNOUNCE] monotone 0.21 released |
Date: |
Tue, 19 Jul 2005 07:32:19 +0200 (CEST) |
In message <address@hidden> on Mon, 18 Jul 2005 21:35:23 -0600, Derek Scherger
<address@hidden> said:
derek> random thought, prompted by the fact that I don't know whether
derek> the --exclude value is persisted as a db var... would
derek>
derek> MT/netsync/server
derek> MT/netsync/include
derek> MT/netsync/exclude
derek>
derek> be a better place than the database for the defaults
derek> (i.e. current db vars)?
derek>
derek> I've run into at least one case where I have two separate
derek> projects in one db (for no particular good reason) and the
derek> defaults only make sense for one of them.
I can agree with what you say. At the same time, I find it very
comfortable to be able to go to the directory where I store all my
databases and do the following:
for x in db.*; do monotone push --db=$x; done
... without having to look further.
I'd recommend one database per consistent project or project group on
the client side.
Cheers,
Richard
-----
Please consider sponsoring my work on free software.
See http://www.free.lp.se/sponsoring.html for details.
--
Richard Levitte address@hidden
http://richard.levitte.org/
"When I became a man I put away childish things, including
the fear of childishness and the desire to be very grown up."
-- C.S. Lewis