CN112363990A - Design file online version management method and device - Google Patents
Design file online version management method and device Download PDFInfo
- Publication number
- CN112363990A CN112363990A CN202011242175.5A CN202011242175A CN112363990A CN 112363990 A CN112363990 A CN 112363990A CN 202011242175 A CN202011242175 A CN 202011242175A CN 112363990 A CN112363990 A CN 112363990A
- Authority
- CN
- China
- Prior art keywords
- branch
- new
- file
- version
- primary
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/1873—Versioning file systems, temporal file systems, e.g. file system supporting different historic versions of files
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/10—File systems; File servers
- G06F16/18—File system types
- G06F16/182—Distributed file systems
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Data Mining & Analysis (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a design file online version management method and device. The method comprises the following steps: when a user creates an online file, a file version warehouse, a HEAD pointer and a version record are created for the online file, the HEAD pointer is used for pointing to a certain branch, the branch is formed by connecting all versions of the same workspace in series according to modification time, the file workspace refers to actual file content, the branch comprises a main branch and a new branch, when only one branch exists, the branch is called the main branch, and the new branch takes a certain version on the main branch as a starting point; when the file is modified by a user, submitting the modified file version as the latest version to the version warehouse and updating the version record; merging the new branch with the main branch. The device comprises: the device comprises an initial module, a new version creating module and a merging module.
Description
Technical Field
The present application relates to the field of design file version management, and in particular, to a method and an apparatus for online design file version management.
Background
The online version management of the design file generally has the following two modes:
firstly, each computer is provided with a complete local warehouse locally, when the online version of the design file is managed, the modification of the local file needs to be submitted to the local warehouse, the two computers access each other in the same local area network, and the respective modifications are pushed to the other side for cooperation.
The disadvantages of this approach are:
1. the modification of the file cannot be automatically submitted to the version library;
2. when the content of the file is modified in the local warehouse, all members cannot cooperate in real time;
3. push version repository modification is limited by the lan in which the computers must be in the same lan at the same time.
And secondly, each computer is provided with a complete local warehouse locally, when the online versions of the design files are managed, the modification of the local files needs to be submitted to the local warehouse, then the modification of the local warehouse is submitted to a remote warehouse, and the modification is pushed in the remote warehouse to carry out file cooperation.
The disadvantages of this approach are:
1. the file content can be modified only by downloading the file from the remote warehouse to the local warehouse;
2. when the local warehouse modifies the file content, the members can not cooperate in real time, and after the file modification is completed, the modification needs to be submitted to the local warehouse, and then the modification of the local warehouse is submitted to the remote warehouse;
3. the remote repository can only track the records of the modifications submitted by the local repository, and cannot track the modified records of the files in the local repository.
Disclosure of Invention
It is an object of the present application to overcome the above problems or to at least partially solve or mitigate the above problems.
According to an aspect of the present application, there is provided a design file online version management method, including:
when a user creates an online file, a file version warehouse, a HEAD pointer and a version record are created for the online file, the HEAD pointer is used for pointing to a certain branch, the branch is formed by connecting all versions of the same workspace in series according to modification time, the file workspace refers to actual file content, the branch comprises a main branch and a new branch, when only one branch exists, the branch is called the main branch, and the new branch takes a certain version on the main branch as a starting point;
when the file is modified by a user, submitting the modified file version as the latest version to the version warehouse and updating the version record;
merging the new branch with the main branch.
Before said merging the new branch with the main branch, the method further comprises:
submitting a merged application to the main branch by the new branch;
judging whether the main branch has advanced submission or not;
when the primary branch does not have advanced submission, the primary branch approves the merged application, and the advanced submission refers to submission of the primary branch after the new branch is created;
when the advanced submission exists in the main branch, marking the content of the conflict between the working space of the main branch and the working space of the new branch, and prompting a user to modify the working space of the main branch and/or the new branch.
Merging the new branch with the primary branch comprises:
and pointing the working space of the main branch to the current submission to the new branch, deleting the new branch, and finishing the combination.
Merging the new branch with the primary branch comprises:
and creating a new submission on the main branch, deleting the new branch, and completing the combination, wherein the content of the newly submitted file is the same as the content of the newly submitted file on the new branch.
The method further comprises the following steps:
and moving the HEAD pointer to point to the branch to be restored, creating a new branch, switching the HEAD pointer to the new branch, updating the working space of the online file and finishing the rollback of the version of the online file.
According to another aspect of the present application, there is provided a design file online version management apparatus including:
an initial module configured to create a file version repository, a HEAD pointer and a version record for an online file when the online file is created by a user, the HEAD pointer being used to point to a branch formed by all versions of the same workspace concatenated according to modification time, the file workspace referring to actual file content, the branch comprising a main branch and a new branch, when only one branch exists, the branch being called the main branch, the new branch starting from a version on the main branch;
the new version creating module is used for submitting the modified file version as the latest version to the version warehouse and updating the version record when the file is modified by a user; and
a merging module configured to merge the new branch with the primary branch.
The device further comprises:
an application module configured to submit a merged application from the new branch to the primary branch;
a determination module configured to determine whether there is a look ahead commit for the primary branch;
an approval module configured to approve the merged application by the primary branch when there is no advance submission by the primary branch, the advance submission referring to a submission that occurred by the primary branch after the new branch was created;
a conflict resolution module configured to mark content for which the workspace of the primary branch conflicts with the workspace of the new branch when there is a lead submission by the primary branch and prompt a user to modify the workspace of the primary branch and/or the new branch.
The merging module comprises:
a workspace transfer sub-module configured to direct a workspace of the primary branch to the current commit to the new branch,
a first delete submodule configured to delete the new branch, completing the merge.
The merging module comprises:
a new commit creating sub-module configured to create a new commit at said primary branch;
a second delete submodule configured to delete the new branch, completing the merge, the newly submitted file content being the same as the newly submitted file content on the new branch.
The device further comprises:
and the rollback module is configured to move the HEAD pointer to point to the branch to be restored, create a new branch, switch the HEAD pointer to the new branch, update the working space of the online file and complete rollback of the version of the online file.
According to the design file online version management method and device, the distributed version control system is innovatively applied to the online file, version management of the online file and team real-time cooperation are achieved by tracking modification submitted by the online file in real time and pushing the modification to other file branches, and compared with the method that the file is downloaded from a remote library to a local library, the file is modified and submitted to the local library, and then the local library is modified and submitted to the remote library branches, the method and device only need to consider pushing modification examination and approval and complete combination.
The above and other objects, advantages and features of the present application will become more apparent to those skilled in the art from the following detailed description of specific embodiments thereof, taken in conjunction with the accompanying drawings.
Drawings
Some specific embodiments of the present application will be described in detail hereinafter by way of illustration and not limitation with reference to the accompanying drawings. The same reference numbers in the drawings identify the same or similar elements or components. Those skilled in the art will appreciate that the drawings are not necessarily drawn to scale. In the drawings:
FIG. 1 is a schematic flow chart diagram of a method for online version management of a design file according to one embodiment of the present application;
FIG. 2 is a schematic diagram of a structure of a primary branch according to one embodiment of the present application;
FIG. 3 is a schematic diagram of the structure of a new branch created on a primary branch according to one embodiment of the present application;
FIG. 4 is a block diagram illustrating the structure of a new branch when a new commit occurs in the new branch according to one embodiment of the present application;
FIG. 5 is a schematic diagram of a fast merge according to one embodiment of the present application;
FIG. 6 is a schematic diagram of disabling fast merge according to one embodiment of the present application;
FIG. 7 is a block diagram illustrating the structure of a main branch and a new branch that conflict when merged according to one embodiment of the present application;
FIG. 8 is a schematic diagram of conflict resolution according to one embodiment of the present application;
FIG. 9 is a schematic diagram of deleting a new branch according to one embodiment of the present application;
FIG. 10 is a schematic diagram of version rollback according to one embodiment of the present application;
FIG. 11 is a schematic diagram of another version fallback according to an embodiment of the present application;
FIG. 12 is a schematic structural diagram of an online design file version management apparatus according to an embodiment of the present application;
FIG. 13 is a block diagram of a computing device, according to one embodiment of the present application;
FIG. 14 is a block diagram of a computer-readable storage medium according to an embodiment of the present application.
Detailed Description
FIG. 1 is a schematic flow chart diagram of a method for online version management of a design file according to one embodiment of the present application. The design file online version management method may generally include:
step S1, when a user creates an online file, creating a file version warehouse, a HEAD pointer and a version record for the online file, wherein the HEAD pointer is used for pointing to a branch, the branch is formed by connecting all versions of the same workspace in series according to modification time, the file workspace refers to actual file content, the branch comprises a main branch and a new branch, when only one branch exists, the branch is called the main branch, and the new branch takes a version on the main branch as a starting point;
step S2, when the file is modified by the user, the modified file version is submitted to the version warehouse as the latest version, and the version record is updated;
and step S3, merging the new branch and the main branch.
The following illustrates the principles of branch creation, merging, and deletion.
The main branch shown in fig. 2 (in fig. 2 to fig. 8, the open circle represents real-time submission, the solid circle represents active submission, the file content is submitted in real time as long as modification occurs, and manual submission is to mark the currently submitted modification and needs manual addition by a user). The version store strings modifications of the submitted file content into a timeline, which is a branch. When there is only one timeline (i.e., only one branch) in a version repository for a file, this branch is the primary branch. Each time a new version is submitted, the pointer of the main branch moves forward one step (the pointer of the branch points to the latest submission of the branch), the line of the main branch is longer and longer along with the continuous submission of the modification, and the working space of the main branch points to the latest submission version on the main branch.
The user may create a new branch based on a version of the main branch, as shown in FIG. 3, and when the new branch is created, the warehouse space creates a new workspace. The new branch may be considered a working copy of the main branch, and creating the new branch may not affect the files of the main branch. The new branch, also called subbranch, in which the content of the workspace can be browsed and edited, is for which both the modification and submission of the workspace are directed, the pointer of the new branch moves one step forward with each submission, while the pointer of the main branch does not change, as shown in fig. 4.
Each file version warehouse at least comprises a main branch and also comprises one or more sub-branches, each branch can have a plurality of versions, each version only stores the modification of the last version of the branch where the version is located, meanwhile, a piece of text information describes the modified content, and all the branches are kept connected through a tree-like relation.
The HEAD pointer is used for pointing to a certain branch under the requirement of a user, the branch pointed by the HEAD pointer is the work space of the current branch, and each branch pointer points to the latest submission of each branch. When the user creates a new branch, the HEAD pointer automatically points to the new branch created.
The file version repository is capable of tracking and managing modifications to the current workspace content. The user modifies the file, and in the modification process, if the user considers that a new version can be formed, the user can mark the currently recorded modification and write the modification description of the new version into the mark. And when the modification is finished, the formed new version can be automatically submitted to the version warehouse.
The sharing of the new branch by each member of the team is realized in the following two ways:
1. merging the file content of the new branch into the main branch, wherein the team member can see the file content of the new branch in the main branch;
2. in the new branch, the team member is allowed to view the file content of the branch by setting the authority.
For the 1 st mode, merging the new branch created by the user with the main branch specifically includes: submitting a merged application to the main branch by the new branch; and after the main branch approves the merging application, merging the new branch created by the user with the main branch.
Merging the new branch to the main branch, sending a merging application from the new branch to the main branch (different member authorities need to be set for the branch in advance, and members with management authorities can approve merging and execute merging), wherein after receiving the merging application, the members with management authorities do not immediately approve the merging application, but need to judge whether the main branch is submitted in advance;
when the primary branch does not have advanced submission, the merging application can be approved, and then merging is performed, wherein the advanced submission refers to submission of the primary branch after the new branch is created; two ways are combined: the first is fast merge, as shown in fig. 5, the workspace of the main branch is referred to the current submission to the new branch, and the new branch is deleted, and after the branch is deleted, the branch information is lost; the second is to disable fast merge, as shown in fig. 6, a new submission is created in the main branch, the content of the file of the new submission is the same as the content of the file newly submitted in the new branch, the new branch is deleted, merge is completed, and after the workspace of the new branch is deleted, branch information can be seen from the branch history;
when the advanced submission exists in the main branch, as shown in fig. 7, if the conflict may occur when the merging is directly performed, marking the content of the conflict between the workspace of the main branch and the workspace of the new branch, and prompting the user to modify the workspace of the main branch or the workspace of the new branch, at this time, the conflict needs to be manually solved by the user, the conflict is solved by modifying the workspace of the main branch, writing the submission description in, submitting a new version, as shown in fig. 8, and deleting the new branch, as shown in fig. 9, so as to complete the merging.
On the basis of the above steps S1 to S3, the method may further include:
version rollback: according to the requirement of a user, moving the HEAD pointer to point to a retroversion target branch, and meanwhile, updating the working space of the online file to finish the retroversion of the online file;
when the content of the file is disturbed, the version can be restored in the modified snapshot record, that is, the HEAD pointer is moved to point to the branch to be restored, and the workspace of the file is updated synchronously. After the version is backed, when a new modification is submitted under a certain submission, a new branch is automatically created, the HEAD pointer is switched to the new branch, and the new modification is submitted in the new branch. After rolling back to a version, if it is desired to revert to a new version, it can be determined in the operational history which version to roll back to. And then find the version in the modified snapshot record to restore. It is also possible to move the branch pointer according to the user's request to point to a branch, restore to the commit pointed by the branch, then create a new branch based on the commit, and then point to the new branch by the HEAD pointer, and at the same time, update the workspace of the online file to complete version rollback, as shown in fig. 11.
The following illustrates the principles of branch creation, merging, and deletion.
In summary, the embodiments of the present application have the following features:
1. each design file is an online version management warehouse, each warehouse is provided with a main branch and a plurality of sub-branches, each branch can be provided with a plurality of versions, each version only stores the modification of the last version on the branch, meanwhile, a piece of text information describes the modified content, and the branches are kept connected through a tree-like relation;
2. team members can create new branches for the design files and submit new versions on the branches;
3. the modification of the team member on the branch can be automatically saved and a new version can be generated, and the team member can also manually submit to generate the new version;
4. the modifications between different branches do not affect each other;
5. team members can perform collaborative modification on the same branch;
6. team members can switch between branches, and can rollback and cancel the modification submission on a certain branch;
7. team members may submit a "branch merge request" to merge a subbranch (i.e., a new branch) into a principal branch "
8. Team members can review the branch merge request;
9. team members with audit authority can accept the branch merge request and merge the subbranches into the main branch;
10. when a conflict occurs between branches, the conflict between the branches can be resolved and branch merging can be completed by on-line.
11. The main branches in the two independent online file version warehouses can be merged according to a merging branch method, and pushing of modified contents is achieved. "
As shown in fig. 12, an embodiment of the present application further provides an online design file version management apparatus, including:
an initial module 1 configured to create a file version repository, a HEAD pointer and a version record for an online file when the online file is created by a user, the HEAD pointer being used to point to a branch formed by all versions of the same workspace concatenated according to modification time, the file workspace referring to actual file content, the branch including a main branch and a new branch, when only one branch exists, the branch is called the main branch, and the new branch starts from a version on the main branch;
the new version creating module 2 is used for submitting the modified file version as the latest version to the version warehouse and updating the version record when the file is modified by a user; and
a merging module 3 configured to merge the new branch with the main branch.
The device further comprises:
an application module configured to submit a merged application from the new branch to the primary branch;
a determination module configured to determine whether there is a look ahead commit for the primary branch;
an approval module configured to approve the merged application by the primary branch when there is no advance submission by the primary branch, the advance submission referring to a submission that occurred by the primary branch after the new branch was created;
a conflict resolution module configured to mark content for which the workspace of the primary branch conflicts with the workspace of the new branch when there is a lead submission by the primary branch and prompt a user to modify the workspace of the primary branch and/or the new branch.
The merging module comprises:
a workspace transfer sub-module configured to direct a workspace of the primary branch to the current commit to the new branch,
a first delete submodule configured to delete the new branch, completing the merge.
The merging module comprises:
a new commit creating sub-module configured to create a new commit at said primary branch;
a second delete submodule configured to delete the new branch, completing the merge, the newly submitted file content being the same as the newly submitted file content on the new branch.
The device further comprises:
and the rollback module is configured to move the HEAD pointer to point to the branch to be restored, and meanwhile, update the working space of the online file to complete rollback of the version of the online file.
The design file online version management apparatus according to the embodiment of the present application is capable of executing the steps of the design file online version management method according to the embodiment of the present application, and the principle and effect thereof are not described herein again.
This application embodiment also provides a computing device, referring to fig. 13, comprising a memory 1120, a processor 1110 and a computer program stored in said memory 1120 and executable by said processor 1110, the computer program being stored in a space 1130 for program code in the memory 1120, the computer program implementing, when executed by the processor 1110, the method steps 1131 for performing any of the methods according to the invention.
The embodiment of the application also provides a computer readable storage medium. Referring to fig. 14, the computer readable storage medium comprises a storage unit for program code provided with a program 1131' for performing the steps of the method according to the invention, which program is executed by a processor.
The embodiment of the application also provides a computer program product containing instructions. Which, when run on a computer, causes the computer to carry out the steps of the method according to the invention.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed by a computer, cause the computer to perform, in whole or in part, the procedures or functions described in accordance with the embodiments of the application. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that incorporates one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
Those of skill would further appreciate that the various illustrative components and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, computer software, or combinations of both, and that the various illustrative components and steps have been described above generally in terms of their functionality in order to clearly illustrate this interchangeability of hardware and software. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the implementation. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.
It will be understood by those skilled in the art that all or part of the steps in the method for implementing the above embodiments may be implemented by a program, and the program may be stored in a computer-readable storage medium, where the storage medium is a non-transitory medium, such as a random access memory, a read only memory, a flash memory, a hard disk, a solid state disk, a magnetic tape (magnetic tape), a floppy disk (floppy disk), an optical disk (optical disk), and any combination thereof.
The above description is only for the preferred embodiment of the present application, but the scope of the present application is not limited thereto, and any changes or substitutions that can be easily conceived by those skilled in the art within the technical scope of the present application should be covered within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (10)
1. An online design file version management method comprises the following steps:
when a user creates an online file, a file version warehouse, a HEAD pointer and a version record are created for the online file, the HEAD pointer is used for pointing to a certain branch, the branch is formed by connecting all versions of the same workspace in series according to modification time, the file workspace refers to actual file content, the branch comprises a main branch and a new branch, when only one branch exists, the branch is called the main branch, and the new branch takes a certain version on the main branch as a starting point;
when the file is modified by a user, submitting the modified file version as the latest version to the version warehouse and updating the version record;
merging the new branch with the main branch.
2. The method of claim 1, wherein prior to said merging the new branch with the primary branch, the method further comprises:
submitting a merged application to the main branch by the new branch;
judging whether the main branch has advanced submission or not;
when the primary branch does not have advanced submission, the primary branch approves the merged application, and the advanced submission refers to submission of the primary branch after the new branch is created;
when the advanced submission exists in the main branch, marking the content of the conflict between the working space of the main branch and the working space of the new branch, and prompting a user to modify the working space of the main branch and/or the new branch.
3. The method of claim 2, wherein merging the new branch with the primary branch comprises:
and pointing the working space of the main branch to the current submission to the new branch, deleting the new branch, and finishing the combination.
4. The method of claim 2, wherein merging the new branch with the primary branch comprises:
and creating a new submission on the main branch, deleting the new branch, and completing the combination, wherein the content of the newly submitted file is the same as the content of the newly submitted file on the new branch.
5. The method according to any one of claims 1-4, further comprising:
and moving the HEAD pointer to point to the branch to be restored, creating a new branch, switching the HEAD pointer to the new branch, updating the working space of the online file and finishing the rollback of the version of the online file.
6. An online version management apparatus for a design file, comprising:
an initial module configured to create a file version repository, a HEAD pointer and a version record for an online file when the online file is created by a user, the HEAD pointer being used to point to a branch formed by all versions of the same workspace concatenated according to modification time, the file workspace referring to actual file content, the branch comprising a main branch and a new branch, when only one branch exists, the branch being called the main branch, the new branch starting from a version on the main branch;
the new version creating module is used for submitting the modified file version as the latest version to the version warehouse and updating the version record when the file is modified by a user; and
a merging module configured to merge the new branch with the primary branch.
7. The apparatus of claim 6, further comprising:
an application module configured to submit a merged application from the new branch to the primary branch;
a determination module configured to determine whether there is a look ahead commit for the primary branch;
an approval module configured to approve the merged application by the primary branch when there is no advance submission by the primary branch, the advance submission referring to a submission that occurred by the primary branch after the new branch was created;
a conflict resolution module configured to mark content for which the workspace of the primary branch conflicts with the workspace of the new branch when there is a lead submission by the primary branch and prompt a user to modify the workspace of the primary branch and/or the new branch.
8. The apparatus of claim 7, wherein the merging module comprises:
a workspace transfer sub-module configured to direct a workspace of the primary branch to the current commit to the new branch,
a first delete submodule configured to delete the new branch, completing the merge.
9. The apparatus of claim 7, wherein the merging module comprises:
a new commit creating sub-module configured to create a new commit at said primary branch;
a second delete submodule configured to delete the new branch, completing the merge, the newly submitted file content being the same as the newly submitted file content on the new branch.
10. The apparatus of any one of claims 6-9, further comprising:
and the rollback module is configured to move the HEAD pointer to point to the branch to be restored, create a new branch, switch the HEAD pointer to the new branch, update the working space of the online file and complete rollback of the version of the online file.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011242175.5A CN112363990A (en) | 2020-11-09 | 2020-11-09 | Design file online version management method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011242175.5A CN112363990A (en) | 2020-11-09 | 2020-11-09 | Design file online version management method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112363990A true CN112363990A (en) | 2021-02-12 |
Family
ID=74509098
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011242175.5A Pending CN112363990A (en) | 2020-11-09 | 2020-11-09 | Design file online version management method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112363990A (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1318168A (en) * | 1998-02-04 | 2001-10-17 | 英特沃汶股份有限公司 | System and method for website development |
| US20080005164A1 (en) * | 2003-06-24 | 2008-01-03 | Terrence Yee | System and method for website development involving journaling and parent maps replacement |
| CN107391968A (en) * | 2017-08-18 | 2017-11-24 | 武汉斗鱼网络科技有限公司 | A kind of method and device for realizing privately owned pod issues control of authority |
| US20180084086A1 (en) * | 2016-09-19 | 2018-03-22 | Palantir Technologies Inc. | Version control machine |
| CN109308188A (en) * | 2018-09-25 | 2019-02-05 | 四川长虹电器股份有限公司 | A kind of edition control method and system based on block chain |
-
2020
- 2020-11-09 CN CN202011242175.5A patent/CN112363990A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1318168A (en) * | 1998-02-04 | 2001-10-17 | 英特沃汶股份有限公司 | System and method for website development |
| US20080005164A1 (en) * | 2003-06-24 | 2008-01-03 | Terrence Yee | System and method for website development involving journaling and parent maps replacement |
| US20180084086A1 (en) * | 2016-09-19 | 2018-03-22 | Palantir Technologies Inc. | Version control machine |
| CN107391968A (en) * | 2017-08-18 | 2017-11-24 | 武汉斗鱼网络科技有限公司 | A kind of method and device for realizing privately owned pod issues control of authority |
| CN109308188A (en) * | 2018-09-25 | 2019-02-05 | 四川长虹电器股份有限公司 | A kind of edition control method and system based on block chain |
Non-Patent Citations (1)
| Title |
|---|
| 刘凯数据分析: ""廖雪峰Git教程笔记"", pages 4 - 12, Retrieved from the Internet <URL:https://blog.csdn.net/cliukai/article/details/91357864> * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10664362B2 (en) | Recovery processing for database in persistent system | |
| US9183236B2 (en) | Low level object version tracking using non-volatile memory write generations | |
| US9690671B2 (en) | Manifest-based snapshots in distributed computing environments | |
| US9020887B2 (en) | Managing the status of documents in a distributed storage system | |
| US7587433B2 (en) | Method and system for in-place updating content stored in a storage device | |
| US8660986B2 (en) | Preserving user intent in merging ordered objects | |
| US20070101256A1 (en) | Perfect source control | |
| US10430281B2 (en) | Space efficient cascading point in time copying | |
| US20080027998A1 (en) | Method and apparatus of continuous data protection for NAS | |
| US20120297363A1 (en) | Inferred and shared source control integration across mulitiple program development tools | |
| JP2019519025A (en) | Division and movement of ranges in distributed systems | |
| CN109542682B (en) | Data backup method, device, equipment and storage medium | |
| US20070143242A1 (en) | Disk-based cache | |
| US20100088270A1 (en) | Data versioning concept including time dependency and active and inactive states | |
| CN107016047A (en) | Document query, document storing method and device | |
| JP5721056B2 (en) | Transaction processing apparatus, transaction processing method, and transaction processing program | |
| US9268755B2 (en) | Performing persistent undo and redo operation within computer software | |
| CN111090701B (en) | Service request processing method, device, readable storage medium and computer equipment | |
| CN112363990A (en) | Design file online version management method and device | |
| CN112148354B (en) | Game starting method and device | |
| JP4437116B2 (en) | Document file movement tracking device, document file movement tracking system, document file movement tracking method and program | |
| KR102007610B1 (en) | Distributed versioning tool of spatial information and method for managing distributed version of spatial information using same | |
| JP2010061200A (en) | Document management system and operation history display method | |
| CN115826880B (en) | Local caching method, device, system, medium and equipment of object storage system | |
| JP3064944B2 (en) | Data recovery method and data recovery method for computer system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |