It's quite possible this has been fixed and that I need to upgrade from
mtn 0.40; it's the mtn provided with my OS. It's conceivable that this
is a version-skew problem, because the other machine with a copy of this
repository is running debian-testing, with presumably a different
monotone.
On Wed, Mar 31, 2010 at 04:44:34PM -0400, hend...@topoi.pooq.com wrote:
Actually, even worse version skew is a real possibility. A month ago I
was running this machine under Debian testing, so it's possible this
very data base has been modified by a monotone more recent than 0.40. I
went
Am 31.03.10 22:26, schrieb hend...@topoi.pooq.com:
It's quite possible this has been fixed and that I need to upgrade from
mtn 0.40; it's the mtn provided with my OS. It's conceivable that this
is a version-skew problem, because the other machine with a copy of this
repository is running
Am 28.03.10 18:17, schrieb Stephen Leake:
Stephen Leake stephen_le...@stephe-leake.org writes:
function gds_update_all()
local workspaces = gds_find_workspaces (gds_missions)
for _, ws in pairs(workspaces) do
-- cd(../ .. ws)
-- mtn (update)
Am 30.03.10 19:11, schrieb Thomas Keller:
Am 31.03.10 22:26, schrieb hend...@topoi.pooq.com:
It's quite possible this has been fixed and that I need to upgrade from
mtn 0.40; it's the mtn provided with my OS. It's conceivable that this
is a version-skew problem, because the other machine
Am 31.03.10 00:12, schrieb Stephen Leake:
I added a new Lua function 'change_workspace' (cmd_automate.cc in
f0b5f85a97853d52f94fd3aab2606ba093a40bff), which basically calls
paths.cc go_to_workspace.
[...]
Any comments on 'automate update' or 'change_workspace'?
Looks good in general, a few