[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Monotone-commits-nodiffs] Revision a9ac940add73b1d6d9b6a12ddffc4dd344a7
From: |
monotone |
Subject: |
[Monotone-commits-nodiffs] Revision a9ac940add73b1d6d9b6a12ddffc4dd344a76e08 |
Date: |
Mon, 14 Jun 2010 20:20:06 +0200 |
-----------------------------------------------------------------
Revision: a9ac940add73b1d6d9b6a12ddffc4dd344a76e08
Ancestor: 8fb30824944061ec4330c5d70449e7699f02b583
Author: address@hidden
Date: 2010-05-23 23.32.45
Branch: net.venge.monotone.experiment.database-management
Modified files:
tests/clone_creates_right__MTN_options/__driver__.lua
ChangeLog:
The behaviour of clone slightly changed for which this test had to be
adapted: Before it was possible to pull data into the same database from
which they were pulled, but this now correctly aborts with a
"database is locked" error. To show the original (anticipated) functionality
still works, we pull from the copied database (and rename it slightly)
and check we either have the same database just as the original workspace
set for the newly cloned workspace or alternatively have initialized a
new and specific database for that.
monotone --db={your.database} diff
--revision=8fb30824944061ec4330c5d70449e7699f02b583
--revision=a9ac940add73b1d6d9b6a12ddffc4dd344a76e08
----------------------------------------------------------------------
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Monotone-commits-nodiffs] Revision a9ac940add73b1d6d9b6a12ddffc4dd344a76e08,
monotone <=