[darcs-devel] [issue2213] last regrets doesn't respect dependencies when going back
Owen Stephens
darcs at owenstephens.co.uk
Mon Jul 23 16:17:04 UTC 2012
On 23 July 2012 16:04, Florent Becker <florent.becker at ens-lyon.org> wrote:
> It's not clear to me what the right behaviour is: it depends on why the
> user is using 'k'. If it's because they didn't get a chance to see 'b'
> while they expected to see it, they will probably appreciate to see it.
> The current behaviour is also consistent with what 'k' does when not at
> the last regrets prompt.
I suppose I'd expect k to go back to the "dependency depth" you've already
seen. An example:
Patches (in repo order): A,B,C,D,E
Dependencies: B and C depend on A, E depends on D
When selecting from all the patches, if I say:
y,y,n,n
I'd have selected A and B.
If I then hit k 4 times I'd like to be presented with (in this order):
D,C,B,A
since I've already "unfolded" A, "revealing" its dependencies.
I'm not sure if this is sensible or not as a behaviour for 'k', but it seems
more consistent with the "forwards" behaviour of patch selection. Maybe
this is
a crazy idea though!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osuosl.org/pipermail/darcs-devel/attachments/20120723/155ae98d/attachment.html>
More information about the darcs-devel
mailing list