Issue 2283: darcs get --tag gets more patches than it should - Darcs bug tracker

Title	darcs get --tag gets more patches than it should
Priority	critical	Status	duplicate
Milestone		Resolved in	2.10.0
Superseder	get --tag gets too many patches if tag is dirty View: 2199	Nosy List	bfrk
Assigned To		Topics

Created on 2012-12-18.12:53:18 by bfrk, last changed 2014-04-09.20:35:53 by bfrk.

Messages
msg16433 (view)	Author: bfrk	Date: 2012-12-18.12:53:16
When I do darcs get --tag=X I get more patches than I asked for! It seems darcs get --tag just obliterates patches from the end of the repo untill it hits the tag. This is very, very bad. The current behaviour means I cannot use darcs get --tag to reliably get a certain set of patches. Tags are the only way in darcs to identify a version (a set of patches). I think darcs get --tag=X repo and darcs initialize darcs pull --tag=X repo should always give the same result but it appears that this is not the case: the latter works, the former does not.
msg16434 (view)	Author: bfrk	Date: 2012-12-18.12:53:51
Forgot: this was with darcs-2.8.0
msg16435 (view)	Author: owst	Date: 2012-12-18.13:38:31
This is the same as issue2199
msg16437 (view)	Author: bfrk	Date: 2012-12-18.14:26:45
sorry, i did a quick search but nothing related came up

History
Date	User	Action	Args
2012-12-18 12:53:18	bfrk	create
2012-12-18 12:53:52	bfrk	set	messages: + msg16434
2012-12-18 13:38:32	owst	set	status: unknown -> duplicate messages: + msg16435 superseder: + get --tag gets too many patches if tag is dirty
2012-12-18 14:26:46	bfrk	set	messages: + msg16437
2014-04-09 20:35:53	bfrk	set	resolvedin: 2.10.0