Eric Kow wrote:
On Fri, Jul 17, 2009 at 10:30:07 -0400, Nathan Gray wrote:
My use case is when we discover a bug the day after a launch, and need
to rollback a patch. We tag each deployment, and would like to keep
that history. Currently we have to unpull the tag, then we usually
just unpull the offending patch and re-tag. But then the history of
us tagging, needing to remove a patch, and re-tagging are lost. All
that remains is a tag showing we deployed a day late.
Unpulling the tag, rolling back and pulling the tag back in should
also work, right?
It's easier than that: you just tell rollback to "rollback" the tag(s)
that is blocking you, which doesn't actually do anything because darcs
doesn't have a tag primitive patch inverse, and then darcs will prompt
you for the patches in that tag. It feels like an odd thing to do, and
my assumption is that it is the only remaining artifact of patch
dependencies in rollback.
The auto-generated rollback summary will include the tag(s), but that
actually ends up being useful landmark information telling you how far
back a patch was. You can also just delete those lines in your long
comment editor.
Certainly may be something to make easier/more obvious in future, though.
--
--Max Battcher--
http://worldmaker.net
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users
