[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Monotone-commits-nodiffs] Revision 0e9cd3fd6a62683c0c768943a629cf02e97b
From: |
monotone |
Subject: |
[Monotone-commits-nodiffs] Revision 0e9cd3fd6a62683c0c768943a629cf02e97b77e5 |
Date: |
Tue, 24 Oct 2006 21:08:04 +0200 |
-----------------------------------------------------------------
Revision: 0e9cd3fd6a62683c0c768943a629cf02e97b77e5
Ancestor: fe9578cc2935d12a41a9e257ee63d8777f2a59be
Author: Timothy Brownawell <address@hidden>
Date: 2006-10-24T18:13:09
Branch: net.venge.monotone
Added files:
tests/netsync_epoch_refinement/__driver__.lua
Added directories:
tests/netsync_epoch_refinement
Modified files:
ChangeLog netsync.cc testsuite.lua
ChangeLog:
2006-10-24 Timothy Brownawell <address@hidden>
Fix an epoch refinement bug. If we already have an epoch for a branch
we're receiving and don't have any revisions for, we will be re-sent
that epoch. There is code to ignore received items that we already
have. This code needs to call maybe_note_epochs_finished() for
epoch items.
monotone --db={your.database} diff
--revision=fe9578cc2935d12a41a9e257ee63d8777f2a59be
--revision=0e9cd3fd6a62683c0c768943a629cf02e97b77e5
----------------------------------------------------------------------
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [Monotone-commits-nodiffs] Revision 0e9cd3fd6a62683c0c768943a629cf02e97b77e5,
monotone <=