| 2006-06-09 15:17:56 |
Gerald Carter |
bug |
|
|
added bug |
| 2006-06-09 15:44:11 |
Gerald Carter |
title |
Vageu python traceback when rnuning 'bzr {info,pull}' on an incomplete tree |
Vague python traceback when rnuning 'bzr {info,pull}' on an incomplete tree |
|
| 2006-09-28 22:52:23 |
John A Meinel |
title |
Vague python traceback when rnuning 'bzr {info,pull}' on an incomplete tree |
Vague python traceback when running 'bzr {info,pull}' on an incomplete tree |
|
| 2006-10-10 06:56:48 |
John A Meinel |
bzr: status |
Unconfirmed |
Confirmed |
|
| 2006-10-10 06:56:48 |
John A Meinel |
bzr: importance |
Undecided |
Wishlist |
|
| 2006-10-10 06:56:48 |
John A Meinel |
bzr: statusexplanation |
|
Canceling rsync while it is running creates a corrupted repository. We should be more aware of this, and exit more gracefully.
1) The repository layout could be tweaked so that rsync also supports our write ordering (index files should come after data files, inventory and revisions should come after knits).
2) Better errors could be given. Though when a repository is randomly corrupted, there is only so much that you can do. |
|
| 2017-11-09 00:40:01 |
Jelmer Vernooij |
tags |
|
check-for-breezy |
|
| 2019-06-29 09:16:12 |
Jelmer Vernooij |
tags |
check-for-breezy |
|
|
