REVISION CONTROL SYSTEM AND METHOD
1 Assignment
0 Petitions
Accused Products
Abstract
There is provided a file revision-control system, method and apparatus configured for storing and managing a revision history log, and for enabling to track and manage, compare and retrieve revisions including, current-revisions stored on a designated reference area, past-revisions stored in a predefined storage area and also past-revisions which were previously on a reference area. According to certain embodiments of the invention, each revision of a file is represented by a revision entry in a revision history log, which can be stored and managed in a designated data-repository. A revision entry stores data corresponding to at least one revision, while the revisions themselves may be stored on a designated data-repository. A progression path refers to one or more revision entries which represent the progression of a file over time. In case that a revision is branched into more than one revisions, each such revision will constitute a different progression path.
-
Citations
133 Claims
-
1-103. -103. (canceled)
-
104. A revision control system comprising:
-
a revision engine associated with at least one processor and operable to access at least one file-system and comprising; a file-system monitor operable to access and monitor said file system and identify a modification event which occurred in respect of a file or folder within a reference area in said file system; a revision manager responsive to said modification event for; creating a new revision entry in a revision history log, the new revision entry corresponding to the modification event; identifying a relevant revision entry in said revision history log corresponding to a revision of said file or folder with respect to which said modification event was implemented; and linking said new revision entry with said relevant revision entry, thereby extending a progression path representing a progression of revisions of said file or folder. - View Dependent Claims (105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117)
-
-
118. A method of revision control, the method comprising:
-
with the help of a processor; accessing and monitoring a file-system and identifying a modification event which occurred in respect of a file or folder within a reference area in said file system; in response to said modification event; creating a new revision entry in a revision history log, the new revision entry corresponding to the modification event; identifying a relevant revision entry in said revision history log corresponding to a revision of said file or folder with respect to which said modification event was implemented; and linking said new revision entry with said relevant revision entry, thereby extending a progression path representing a progression of revisions of said file or folder. - View Dependent Claims (119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130)
-
-
131. A revision control system comprising:
-
a revision engine associated with at least one processor and operable to access at least one file-system and comprising; a file-system monitor operable to access and monitor said file system and identify a modification event which occurred in respect of a file or folder within a reference area in said file system; a revision manager responsive to said modification event for; creating a new revision entry in a revision history log, the new revision entry corresponding to the modification event; identifying a relevant revision entry in said revision history log corresponding to a revision of said file or folder with respect to which said modification event was implemented; and linking said new revision entry with said relevant revision entry, thereby extending a progression path representing a progression of revisions of said file or folder; identifying that along a first progression path associated with said relevant revision entry, a second revision entry exists, which corresponds to a modification of a revision associated with said relevant revision entry;
said progression path being another progression path linking said relevant revision entry with said new revision entry; andmaintaining both said first progression path and said another progression path associated with said relevant revision entry, said relevant revision entry being indicative of a past revision common to both progression paths; wherein a revision entry in said revision history log includes at least one data-element and wherein said revision engine is further operable to identify within said revision history log, at least one other revision entry with at least one respective data-element which is identical to said at least one data-element, wherein one of said revision entry and said at least one other revision entry is located in said first progression path and the other is located in said new progression path; and
determine, based on at least said at least one identical data element, a historical relationship between revisions represented by said revision entry and said at least one other revision entry.
-
-
132. A program storage device readable by machine, tangibly embodying a program of instructions executable by the machine to perform method steps of revision control, the method comprising:
-
accessing and monitoring a file-system and automatically identifying a modification event which occurred in respect of a file or folder within a reference area in said file system; in response to said modification event; creating a new revision entry in a revision history log, the new revision entry corresponding to the modification event; identifying a relevant revision entry in said revision history log corresponding to a revision of said file or folder with respect to which said modification event was implemented; and linking said new revision entry with said relevant revision entry, thereby extending a progression path representing a progression of revisions of said file or folder.
-
-
133. A revision control system comprising:
-
a revision engine associated with at least one processor and operable to access at least one file-system and comprising; a revision manager responsive to a modification event which occurred in respect of a file or folder within a reference area in said file system, for; creating a new revision entry in a revision history log, the new revision entry corresponding to the modification event; identifying a relevant revision entry in said revision history log corresponding to a revision of said file or folder with respect to which said modification event was implemented; and linking said new revision entry with said relevant revision entry, thereby extending a progression path representing a progression of revisions of said file or folder; identifying that along a first progression path associated with said relevant revision entry, a second revision entry exists, which corresponds to a modification of a revision associated with said relevant revision entry;
said progression path being another progression path linking said relevant revision entry with said new revision entry; andmaintaining both said first progression path and said another progression path associated with said relevant revision entry, said relevant revision entry being indicative of a past revision common to both progression paths.
-
Specification