Missing: dirstate#invalidate
Reported by Michael J. Edgar | August 18th, 2009 @ 03:19 AM | in Full Mercurial Featureset
Invalidation: error recovery
We need to port the invalidation methods for the DirState and local repository-related classes. Thus, if an error occurs during an operation that affects the dirstate, we can invalidate it and rebuild it later. Right now, these methods are ignored.
Steps to fix:
- Take a look at how it's done in the Python
- Determine if we like their approach or if we're better off
doing our own thing
- Implement invalidation, ruby-like interface (no direct
port)
- Search for all places (in mercurial's source) where invalidation could be used. Because I'm lazy. Add it in every corresponding place in the Ruby (if it's sensible!)
Comments and changes to this ticket
-
-
seydar November 25th, 2009 @ 01:49 PM
i went back in time and fixed this one so... it was already fixed. (See DirState#invalidate)
this makes sense considering this is a bug report from august -
seydar November 25th, 2009 @ 10:52 PM
- State changed from “new” to “resolved”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Rethink Version Control.- http://amp.carboni.ca/
Amp aims to put control of version-control software in your hands as a developer. The entire system is written in Ruby (with C extensions to improve performance), and aims to implement all major VCS's in Ruby. Currently, Mercurial is implemented.
Other features:
Commands are first-class members of the system - drop in an "Ampfile" in your repository, and you can add commands to amp in the same manner you add commands to rake (only with far, far more power!)
Documentation is one of our biggest priorities. We require all methods to be documented - even comically simple ones.
Heavy testing.
Multiple "workflows" - use git's commands to power a mercurial repository.
Add hooks/callbacks in minutes.
Michael J. Edgar