monotone-commits-nodiffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Monotone-commits-nodiffs] Revision 5832e6ef0dfd2b605591af26fd9d3437dbe7


From: monotone
Subject: [Monotone-commits-nodiffs] Revision 5832e6ef0dfd2b605591af26fd9d3437dbe73253
Date: Fri, 2 Feb 2007 23:04:56 +0100

-----------------------------------------------------------------
Revision: 5832e6ef0dfd2b605591af26fd9d3437dbe73253
Ancestor: f612f74889c12998e416dfafe7ee941fb909311a
Author: Thomas Moschny <address@hidden>
Date: 2007-02-02T21:24:41
Branch: net.venge.monotone.experiment.annotate.roster_deltas

Modified files:
        ChangeLog annotate.cc database.cc database.hh
        roster_delta.cc roster_delta.hh

ChangeLog: 

2007-02-02  Thomas Moschny  <address@hidden>

        * roster_delta.{cc|hh}
        (get_markings_from_roster_delta, get_content_from_roster_delta):
        New functions. Both try to extract node-specific information from
        a single roster delta.

        * database.{cc|hh} (get_markings, get_file_content): New functions
        using roster deltas to find the set of markings resp. the content
        hash for a given node and revision id.

        * annotate.cc (do_annotate_node): Utilize the new methods. Store
        the set of markings and the file content hash in the work_unit for
        the corresponding revision, to avoid fetching the same information
        twice. Don't fetch content hash or markings for marked ancestors,
        as we can deduce that information from the descendants.


monotone --db={your.database} diff 
--revision=f612f74889c12998e416dfafe7ee941fb909311a 
--revision=5832e6ef0dfd2b605591af26fd9d3437dbe73253
----------------------------------------------------------------------




reply via email to

[Prev in Thread] Current Thread [Next in Thread]