Issue 299 Diff not smart about checkpoints

Title Diff not smart about checkpoints
Priority bug Status resolved
Superseder unrecording checkpoint patch quietly breaks things
View: 517
Nosy List beschmi, dagit, droundy, jch, kowey, markstos, tommy
Assigned To Topics

Created on 2006-10-13.10:04:50 by kowey, last changed 2008-09-04.21:29:36 by admin.

Messages
msg1083 (view) Author: kowey Date: 2006-10-13.10:04:37
Import of RT #552

jch <Juliusz.Chroboczek@pps.jussieu.fr> 2005-10-13
--------------------------------------------------
The functions get_matcher and get_before_matcher are not smart enough
about checkpoints. They unconditionally grab a pristine tree (which
might or might not involve patching from the latest checkpoint,
depending on the repo format) and then patch backwards from there.

Instead, they should fetch the checkpoint that's closest to the point
requested, and patch forwards or backwards from there.

We need an interface in the repository interface to find out which
checkpoints are available and pull them out of the repo. In order to
be efficient with Git repos (in the current mapping, David), this
interface should not require that a checkpoint be associated with a
tag.

Ideas for such welcome.

Juliusz
msg2467 (view) Author: markstos Date: 2008-01-13.16:00:32
I believe this is "resolved-in-unstable", because the darcs-2 format doesn't
have checkpointing. See discussion and test in issue517.

Browse related patches: unstable | stable

History
Date User Action Args
2006-10-13 10:04:51koweycreate
2007-08-14 06:17:16koweysettopic: - FromRequestTracker
nosy: + beschmi
2008-01-13 16:00:33markstossetstatus: unread -> resolved-in-unstable
messages: + msg2467
superseder: + unrecording checkpoint patch quietly breaks things
nosy: + markstos
2008-09-04 21:29:36adminsetstatus: resolved-in-unstable -> resolved
nosy: + dagit