32 results about "Version history" patented technology

An apparatus and method of synchronizing a datum between a plurality of stores is disclosed. A version history is associated with the datum in each store. The version history has one or more entries, and each entry has an identifier and a value. The identifier identifies a store that has modified the datum, and the value indicates a number of modifications to the datum made by the store. When synchronizing the datum between stores, the version histories of the datum are compared to determine whether one version history is subordinate to another version history. The datum in the store having the subordinate version history is then replaced with the datum having the dominant version history. When compared, a conflict resolution by a user is required if the version histories are not identical, if the version histories do not have all the same identifiers, and if one version history does not contain all of the identifiers with equal or greater values of those in the other version history.

A system and method for versioning of atomic units of data (such as XML fragments) in a distributed data store are disclosed. The distributed data store may maintain a linear version history for each fragment, such that each has no more than one successor and one predecessor, with no implicit branching. An application programming interface may provide an explicit branching request (indicating an intent to merge modified data in a child branch into its parent branch), along with read, create, create-merge, and/or integrate requests. A reconciliation policy may be specified on a per-application basis, and may include automatic reconciliation using a callback function or interactive reconciliation, with inputs returned to the application. Writes to a minority side of a network partition may be refused unless an explicit branch is requested. Transactions may not be supported in client applications or may be supported through explicit branching. Transactions may be used internally.

A method for file version control, including intercepting a command to access a target file within a computer file system, determining whether or not the intercepted command is directly related to a user editing session, based on at least one behavioral rule, if the determining is affirmative, then storing a copy of the target file within a file version history archive, and adding a reference to the target file to a queue of active files, when the target file is closed, searching the queue of active files for an entry to the target file, if an entry to the target file in the queue of active files is found, then comparing the target file against the stored copy, if the target file is identical to the stored copy, then deleting the copy of the target file from the file version history archive, and clearing the reference to the target file from the queue of active files. A system and a computer-readable storage medium are also described and claimed.

A method of searching a corpus including a plurality of files includes automatically determining, using a processor, a historical ranking for each file using respective changeset information. Search term(s) of a query are received. A textual ranking is determined for each file using the search term(s) and contents of that file. The historical and textual rankings are combined to provide a result ranking. A data processing system includes a storage system storing the corpus including the plurality of files, a processor configured to determine the result rankings, and a user interface system configured to receive query results from the processor and present them to a user.

A method and system are provided to automatically and transparently version files across many desktop applications without requiring the user to take specific action to cause the versioning to occur. Previous versions and versioning information can both be stored using hard links, and the versioning information can be used to determine a version history for a file. Embodiments of the present invention do not require applications to be modified to support this versioning method. Further, using one approach, the application does not even know that the versioning is occurring. The present invention provides an automatic versioning solution that is completely transparent to the user, which causes overwrite operations to be seamlessly co-opted into versioning operations which retain previous document versions instead of overwriting them.

An auto version managing system for software including a search module for searching at least one folder and file structure in the software and for indexing the folder and file, a version managing database (DB) for storing software version information including at least one of a software version, file properties, checksum, and version history, and a checksum calculation part for calculating a checksum of the folder and the file. The system further includes a checksum comparison part for comparing the checksums of the software of an old version that are stored in the version managing DB with the checksums of an upgraded software, and then extracting one of the changed folder(s) and file(s). The system still further includes a DB generation part for storing information about the extracted folder or file in the version managing DB, such that a DB of the software version history can then be automatically generated.

A system and method for displaying an enhanced version history user interface for an online content management system. In one embodiment, a version history user interface includes version history entries that represent primary events and anchor events. In another embodiment, a preview version history user interface is displayed that allows a user to preview a version of a content item. In another embodiment, a restore action process allows a user to restore a previous version of a content item to be the new current version of the content item.

A method, non-transitory computer readable medium, and apparatus that obtains a version history for a plurality of source code files associated with the computer program. At least one defect probability value is generated for each of the plurality of source code files using at least one metric and the obtained version history. One or more of the plurality of source code files having a higher risk of including one or more defects than one or more other of the plurality of source code files are identified based on the generated defect probability values. Information regarding each of the one or more identified source code files is output.

A computer implemented method and apparatus for providing dependency traceability in software configuration management. Per configuration of a subject software program formed of one or more artifacts, a version history of each artifact is maintained. For each artifact, coupled to the respective version history of the artifact is an indication of status of traceability relationship for each indicated version. One implementation employs a traceability object to maintain and provide such status indications. The status indications are view independent and enable dependency traceability relationship of each artifact to be determinable in each configuration employing the artifact.

Described embodiments enable device users to share content items directly from the context of a desktop file system user interface. A share bar is displayed in the file system user interface, where the share bar includes one or more graphical control elements that provide additional functionality with respect to one or more selected content items in the user interface. The additional functionality can include sharing the selected item, moving the item, downloading the item, and viewing sharing status, version history, completion status, comments, or other information about the item.

The present invention provides a method and system for detecting a partial commit of software. A dependency information of the software is extracted from a version history and a bug database. A dimensional matrix containing a set of commit, and relationship information with a set of files with each commit is created from the dependency information. A centrality matrix is computed by performing a first set of matrix transformations on the dimensional matrix. A set of missing files of a partial commit, is identified by performing a second set of matrix transformations on the centrality matrix and a file vector, the file vector including a file dependency information of the partial commit.

A method and an apparatus for version management are provided in the embodiment of that present invention. The system comprises a database for uniformly acquiring and storing the version number of a service mirror. The method comprises: when a new uploaded service image is detected in the system, updating the version number in the version number database of the system based on the newly uploaded service image; when a version upgrade or a version rollback of a service image is required, querying the database based on a version number related to the version upgrade or the version rollback, and performing the version upgrade or the version rollback according to the service image corresponding to the queried version number. The unified management of each service version is realized, the latestversion of the current service and version history information can be easily known, and when the version update caused problems, the old version can be quickly carried out, to ensure the normal operation of the service.

Systems and methods of provisioning data storage and runtime configuration in telecommunications systems and devices. The systems and methods employ at least one decentralized revision control system as a data repository for storing data, such as configuration data, and at least one data provisioning component as an interface for accessing the configuration data stored in the data repository. By employing the decentralized revision control system in conjunction with the data provisioning component, the systems and methods can provide a data storage and runtime configuration provisioning framework that is data agnostic, application agnostic, and user agnostic, while further providing at least the capability of tracking and maintaining the version history of the configuration data.

A version history of each of a plurality of resources is stored in a table. The version history for each resource comprises a set of one or more values for the resource, wherein each value in the version history of a resource indicates the value that the resource had in a particular version of the resource. In response to a request to perform an operation that causes a given resource that is subject to a uniqueness constraint to have a particular value, it is determined whether the uniqueness constraint is violated based on whether any version of any resource other than the given resource has the particular value. The uniqueness constraint is determined to be violated if any version of any resource other than the given resource has the particular value. The uniqueness constraint is not violated by existence of a version of the given resource that has the particular value.

Method and apparatus for managing software configurations include a version history member representing changes between versions of artifacts forming different configurations of a subject software program. Indicated in version history member is any selective merge between artifact versions. Also indicated in the version history member is any subtractive merge between artifact versions. A selective merge arc arid a subtractive merge arc are respective examples.

A computer implemented method, data processing system, and computer usable program code are provided for associating historical events with a user. A historical event is identified for association with the user. A determination is made as to whether the historical event has been certified by a trusted authority in response to identifying the historical event for association with the user. A historical object is created for the historical event if the historical event has been certified by the trusted authority and associated with the user.