Issue 1866: accept some prefix of patchinfo hash for hash matcher

Title	accept some prefix of patchinfo hash for hash matcher
Priority	feature	Status	resolved
Milestone	2.8.0	Resolved in
Superseder		Nosy List	beschmi, dmitry.kurochkin, kowey
Assigned To	beschmi	Topics	Matchers

Created on 2010-06-06.17:23:07 by kowey, last changed 2017-07-31.00:02:03 by gh.

msg11276 (view)

Author: kowey

Date: 2010-06-06.17:23:05

I'm taking the liberty of assigning Benedikt to this because he's
working on the new readable darcs annotate in issue25.

Whatever prefix darcs annotate uses to return the patch info hash, it
seems that our hash matcher should accept.

It seems the key point here is not the implementation, but deciding what
sort of prefix that should be (hence need-action)

Even if we don't have the new darcs annotate by Darcs 2.5 I would
suggest getting this done by then so that we're ready.

History
Date	User	Action	Args
2010-06-06 17:23:07	kowey	create
2010-06-06 17:23:30	kowey	link	issue25 superseder
2010-06-15 20:52:19	admin	set	milestone: 2.5.0
2010-06-15 21:00:12	admin	set	topic: - Target-2.5
2010-07-25 14:35:15	tux_rocker	set	milestone: 2.5.0 -> 2.8.0
2017-07-31 00:02:03	gh	set	status: needs-reproduction -> resolved

Issue 1866 accept some prefix of patchinfo hash for hash matcher