[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Monotone-commits-nodiffs] Revision dd4a3e3380179c1d96e567afc13d4a4b88ff
From: |
monotone |
Subject: |
[Monotone-commits-nodiffs] Revision dd4a3e3380179c1d96e567afc13d4a4b88ff8542 |
Date: |
Mon, 13 Mar 2006 02:06:03 +0100 |
-----------------------------------------------------------------
Revision: dd4a3e3380179c1d96e567afc13d4a4b88ff8542
Ancestor: 30309ca3427acd11df8dfbc8faec0682cb38a954
Author: address@hidden
Date: 2006-03-13T00:42:30
Branch: net.venge.monotone
Modified files:
ChangeLog app_state.cc app_state.hh commands.cc monotone.cc
ChangeLog:
2006-03-12 Richard Levitte <address@hidden>
Some of the monotone commands don't really need to use the data
in MT/options. As a matter of fact, it's even a really bad idea
for some command, for example 'monotone serve'. We must still
check for the MT directory and read whatever is there, just
don't immediately use the data from MT/options. I've done it by
moving the code that processes the data from MT/options in
app_state::allow_workspace to another method, which is then used
separately.
* app_state.cc, app_state.hh (app_state::allow_workspace): The
code that processes data from MT/options and uses the information
is now moved...
(app_state::process_options): ... here.
* commands.cc (struct command, commands::process, CMD, CMT_NO_MT):
Add a per-command flag that says if the particular command needs
to bother with the workspace options or not. CMD_NO_MT is a new
macro to help define commands that don't.
(CMD(serve)): Change into...
(CMD_NO_MT(serve)): ... this.
* monotone.cc (cpp_main): Changed the comment so it matches
reality.
monotone --db={your.database} diff
--revision=30309ca3427acd11df8dfbc8faec0682cb38a954
--revision=dd4a3e3380179c1d96e567afc13d4a4b88ff8542
----------------------------------------------------------------------
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Monotone-commits-nodiffs] Revision dd4a3e3380179c1d96e567afc13d4a4b88ff8542,
monotone <=