monotone-commits-nodiffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Monotone-commits-nodiffs] Revision f953638f72d4b30fc1fe9a0ac21f3e9685a3


From: monotone
Subject: [Monotone-commits-nodiffs] Revision f953638f72d4b30fc1fe9a0ac21f3e9685a37874
Date: Thu, 19 Nov 2009 16:05:36 +0100

-----------------------------------------------------------------
Revision: f953638f72d4b30fc1fe9a0ac21f3e9685a37874
Ancestor: 005d5e5e999c6384eb3249bd4219abaa3fda4f71
Author: address@hidden
Date: 2009-10-23T08:18:09
Branch: net.venge.monotone.guitone

Modified files:
        src/main.cpp src/model/AutomateCommand.cpp
        src/monotone/MonotoneManager.cpp
        src/monotone/MonotoneManager.h
        src/monotone/MonotoneThread.cpp
        src/monotone/MonotoneThread.h

ChangeLog: 

* MonotoneManager.h/cpp: distinguish between abortion and normal termination; 
the cleanup part is the same, however only on abortion we display an error 
message
* main.cpp/MonotoneManager.cpp: register the QProcess error type for Qt's meta 
system in main.cpp, where all the others are registered as well
* MonotoneThread.cpp: ensure that cleanup() is called before aborted() or 
stopped(), so we still have the chance to properly clean up the inner QProcess 
before the thread is deleted externally
* AutomateCommand.cpp: of course if we do not remove an aborted thread from the 
thread map, we get an exception the next time we abort threads and this one is 
still present...


monotone --db={your.database} diff 
--revision=005d5e5e999c6384eb3249bd4219abaa3fda4f71 
--revision=f953638f72d4b30fc1fe9a0ac21f3e9685a37874
----------------------------------------------------------------------




reply via email to

[Prev in Thread] Current Thread [Next in Thread]