Revlogs: check_inline_size
Reported by Michael J. Edgar | August 18th, 2009 @ 03:21 AM | in Full Mercurial Featureset
Revlog#check_inline_size
The RevlogInlineNG revlog format is convenient as it limits IO seeks. However, once the inline file gets too big, we should split it back up into an index and a data file. That method is check_inline_size, and needs to be implemented.
- Port this method from the python. Be reasonable, use ruby-like
techniques.
- Find all places where the mercurial peeps found it necessary
for this validation. Add them in the ruby.
- Look for any other places they might have missed.
Comments and changes to this ticket
-
Michael J. Edgar November 25th, 2009 @ 08:23 AM
- State changed from “new” to “resolved”
-
seydar November 28th, 2009 @ 06:24 AM
- State changed from “resolved” to “open”
This isn't actually done yet (you probably just got a little click-happy). Will look at it now.
-
seydar November 28th, 2009 @ 04:37 PM
I pushed some changes to it last night. It's all good except for one line that is neatly marked by the all-caps comments above it.
-
Michael Edgar November 28th, 2009 @ 07:31 PM
- Assigned user changed from “Michael J. Edgar” to “seydar”
-
seydar November 28th, 2009 @ 08:48 PM
- Assigned user changed from “seydar” to “Michael J. Edgar”
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