Method for managing file in version control system

• US 20070150433A1
• Filed: 12/22/2005
• Published: 06/28/2007
• Est. Priority Date: 12/22/2005
• Status: Abandoned Application

• Current Assignee: MediaTek, Inc.
• Original Assignee: MediaTek, Inc.
• Inventors: Chen, Pei-Wen
• Application Number:
  US11/317,916
• Publication Number:
  US 20070150433A1
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: G06F 8/71 Version control security arrangements therefor G06F21/57; Configuration management

Abstract

A method for managing a target file in a version control system is provided. According to this invention, when a user requests to check-out, check-in, update, or add tags to an target file, the version control system operates on a substitute file instead of the target file. The substitute file is generated based on the target file and is much smaller than the target file. Thus, the time for opening and manipulating files can be saved.

Claims

1. A method for adding an target file into a version control system, comprising the steps of:

generating a substitute file based on the target file;

checking-in the substitute file into said version control system;

selecting a storage space for storing the target file based on a predetermined rule; and

storing the target file into the storage space;

wherein after the target file is stored into the storage space, when a request for accessing the target file is transmitted to said version control system, the substitute file stored in the version control system is first checked-out and the storage space for storing the target file is then found according to the substitute file and the predetermined rule.

2. The method of claim 1, wherein the version control system is a concurrent versions system (CVS).

3. A method for managing a target file comprising N versions, N being a natural number, a substitute file being previously generated based on the N versions of the target file and stored in a version control system, each of the N versions of the target file being respectively stored in a storage space, said method comprising the steps of:

in response to a check-out request transmitted to the version control system for checking-out the target file into a workspace, the following sub-steps being performed;

(a1) judging whether any of the N versions of the target file has been checked-out into said workspace, if NO, performing the sub-steps (a2) through (a4);

(a2) checking-out the substitute file from the version control system into said workspace;

(a3) according to a predetermined rule, finding out the storage space for storing the revision of data; and

(a4) copying the revision of data from the storage space to said workspace.

4. The method of claim 3, wherein if the judging result of the sub-step (a1) is YES, the following sub-step is performed:

(a5) judging whether the revision of data having been checked-out into said workspace is modified in said workspace, if NO, performing the sub-steps (a2) through (a4).

5. The method of claim 4, wherein if the judging result of the sub-step (a5) is YES, the following sub-step is performed:

(a6) sending a first warning to said workspace to indicate a modification has occurred.

6. The method of claim 5, wherein at least one of the N versions of the target file has ever been checked-out into said workspace as a local revision of data, the substitute file has been checked-out into said workspace as a local substitute file, and if the judging result of the sub-step (a5) is YES, the following sub-step is also performed:

(a7) modifying the local substitute file to record that the local revision of data is modified.

7. The method of claim 3, wherein at least one of the N versions of the target file has ever been checked-out into said workspace as a local revision of data, and the substitute file has ever been checked-out into said workspace as a local substitute file, said method further comprising the steps of:

in response to a check-in request transmitted to the version control system for checking-in the local revision of data from the workspace, the following sub-steps being performed;

(b1) judging whether the local revision of data is modified in said workspace, if YES, modifying the local substitute file to record that the local revision of data is modified;

(b2) checking-in the local substitute file into the version control system;

(b3) judging whether a new revision of substitute file has been created, if YES, proceeding to step (b4);

(b4) selecting a new storage space for storing the local revision of data based on said predetermined rule; and

(b5) copying the local revision of data from the workspace into the new storage space.

8. The method of claim 7, wherein if the judging result of the sub-step (b1) is NO, the following sub-step is performed:

(b6) sending a second warning to said workspace to indicate no modification.

9. The method of claim 7, wherein if the judging result of the sub-step (b3) is NO, the following sub-step is performed:

(b7) sending a third warning to said workspace to indicate an unsuccessful check-in.

10. The method of claim 3, wherein at least one of the N versions of the target file has ever been checked-out into said workspace as a local revision of data, and the substitute file has ever been checked-out into said workspace as a local substitute file, said method further comprising the steps of:

in response to an update request transmitted to the version control system for updating the local revision of data, the following sub-steps being performed;

(c1) judging whether the local revision of data is modified in said workspace, if NO, performing the steps (c2) through (c4);

(c2) checking-out the substitute file from the version control system into said workspace;

(c3) according to said predetermined rule, finding out the storage space for storing the revision of data; and

(c4) copying the revision of data from the storage space to said workspace.

11. The method of claim 10, if the judging result of the sub-step (c1) is YES, the following sub-step is performed:

(c6) sending a fourth warning to said workspace to indicate a modification has occurred.

12. The method of claim 3, said method further comprising the steps of:

in response to a tag request transmitted to the version control system for adding a tag to the target file, the following sub-step being performed;

(d1) recording a tag corresponding to the substitute file.

13. The method of claim 3, said method further comprising the steps of:

in response to a log request transmitted to the version control system for viewing a set of history record corresponding to the target file, the following sub-step being performed;

(e1) showing the set of history record recorded in the substitute file.

14. The method of claim 3, wherein the version control system is a concurrent versions system (CVS).

15. A method for managing versions of a target file, the method comprising:

synchronizing a substitute file with a version of the target file;

checking the substitute file, instead of the version of the target file, into a version control system; and

copying the version of the target file into a storage space;

wherein a storage path of the version of the target file is generated so that once the substitute file is identified, the storage path of the version of the target file is found.

16. The method of claim 15, wherein the storage path of the version of the target file is recorded.

17. The method of claim 15, wherein the storage path of the version of the target file is generated according to a predetermined rule.

18. The method of claim 15, wherein the version control system is a concurrent versions system (CVS).

19. The method of claim 15, wherein the step of synchronizing further comprising:

appending current time to the substitute file.

20. The method of claim 15, wherein the step of synchronizing further comprising:

appending a random number to the substitute file.

21. A method for managing versions of a target file, the method comprising:

checking a substitute file, instead of the version of the target file, out of a version control system; and

copying a version of the target file from a storage space;

wherein a storage path of the version of the target file is generated so that once the substitute file is identified, the storage path of the version of the target file is found.

22. The method of claim 21, wherein the version control system is a concurrent versions system (CVS).

23. The method of claim 21, further comprising:

before checking out a substitute file from the version control system, synchronizing substitute file with the version of the target file.