RE: Proposal to implement get_commit_and_merge_ranges from FS

>> Possible solutions:
>> We can maintain this per commit data in a separate place other than the one
>> where revprops sit. Provide mechanisms to retrieve from this location.

>I do not see anything wrong with this as a solution. I assume in BDB
>we would just have a new table for this info (maybe you already do).
>In fsfs we could add a new folder to the repository db named
>"mergeinfo". Whenever a commit is done that alters mergeinfo, you
>could create a file with the same name as the revision that stores
>this information. If the commit does not alter mergeinfo, do not
>create a file. You could even follow the same sharding scheme as the
>revs folder, just for consistency.

>I do not see any problem with this approach.

Thanks, That is what I work on now.

With regards
Kamesh Jayachandran
Received on 2008-01-27 18:58:34 CET