CN115495143A - Patch file making and application method, system, electronic equipment and storage medium - Google Patents

Patch file making and application method, system, electronic equipment and storage medium Download PDF

Info

Publication number
CN115495143A
CN115495143A CN202211204222.6A CN202211204222A CN115495143A CN 115495143 A CN115495143 A CN 115495143A CN 202211204222 A CN202211204222 A CN 202211204222A CN 115495143 A CN115495143 A CN 115495143A
Authority
CN
China
Prior art keywords
patch file
patch
git
command
flag bit
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
Application number
CN202211204222.6A
Other languages
Chinese (zh)
Inventor
黄蓉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Spreadtrum Semiconductor Nanjing Co Ltd
Original Assignee
Spreadtrum Semiconductor Nanjing Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Spreadtrum Semiconductor Nanjing Co Ltd filed Critical Spreadtrum Semiconductor Nanjing Co Ltd
Priority to CN202211204222.6A priority Critical patent/CN115495143A/en
Publication of CN115495143A publication Critical patent/CN115495143A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Computing Systems (AREA)
  • Data Mining & Analysis (AREA)
  • Computer Security & Cryptography (AREA)
  • Stored Programmes (AREA)

Abstract

The invention discloses a patch file making and applying method, a system, electronic equipment and a storage medium, wherein the patch file making method comprises the following steps: acquiring a Git warehouse path of the patch file according to the pwd command; and adding the Git warehouse path to a flag bit of the patch file, wherein the flag bit is the part of the patch file which is firstly analyzed when the patch file is applied to the patch file. According to the invention, the Git warehouse path of the patch file is extended to the flag bit of the patch file, so that when the patch file is applied, a user does not need to find out the Git warehouse corresponding to the correct patch file one by one, the patch file is automatically applied to the Git warehouse corresponding to the patch file, and the efficiency and the convenience for applying the patch file are improved.

Description

Patch file making and application method, system, electronic equipment and storage medium
Technical Field
The invention relates to the technical field of computer programming, in particular to a patch file making and applying method, a patch file making and applying system, electronic equipment and a storage medium.
Background
In the prior art, before a Git open-source distributed version control system applies a patch file, the system must know the correct address of a Git warehouse to which the patch file belongs, otherwise, the application of the patch file fails. However, if a plurality of patch files exist, even if a readme (use description file) is provided, the system knows the corresponding relationship between the patch files and the Git warehouse, and finding the warehouse and then applying the patch files one by one is time-consuming and labor-consuming, so that the efficiency of applying the patch files is reduced, and the use experience of a user is influenced.
Disclosure of Invention
The invention provides a patch file making and applying method, a system, electronic equipment and a storage medium, aiming at overcoming the defect that in the prior art, a system must know the correct address of a Git warehouse to which a patch file belongs, otherwise, the application of the patch file fails.
The invention solves the technical problems through the following technical scheme:
in a first aspect, the present invention provides a method for making a patch file, where the method for making a patch file includes:
acquiring a Git warehouse path of the patch file according to the pwd command;
and adding the Git warehouse path to a flag bit of the patch file, wherein the flag bit is the part of the patch file which is firstly analyzed when the patch file is applied.
Preferably, the step of obtaining the Git warehouse path of the patch file according to the pwd command includes:
saving the Git warehouse path as a string;
the step of adding the Git warehouse path to the flag bit of the patch file comprises:
adding the character string to a flag bit of the patch file;
and/or the presence of a gas in the gas,
the flag bit comprises a head or a tail of the patch file;
and/or the presence of a gas in the gas,
the format of the patch file is a diff format or a patch format.
Preferably, the step of obtaining the Git warehouse path of the patch file according to the pwd command comprises:
receiving a patch file making command, wherein the patch file making command comprises a Git format-patch command and/or a Git diff command.
In a second aspect, the present invention provides a patch file application method, where the patch file application method includes:
analyzing the flag bit of the patch file, wherein the patch file is manufactured by the patch file manufacturing method;
jumping to a Git warehouse under the Git warehouse path of the patch file;
and applying the patch file under the Git warehouse.
Preferably, the step of parsing the flag bit of the patch file includes:
and analyzing the zone bit of the patch file according to the key words of the character strings.
Preferably, the step of parsing the flag bit of the patch file comprises:
receiving a patch application command, wherein the patch application command comprises a Git apply command and/or a Git am command.
In a third aspect, the present invention provides a patch file production system, including:
the acquisition module is used for acquiring a Git warehouse path of the patch file according to the pwd command;
and the manufacturing module is used for adding the Git warehouse path to a flag bit of the patch file, wherein the flag bit is the part of the patch file which is firstly analyzed when the patch file is applied.
In a fourth aspect, the present invention provides a patch file application system, including:
the analysis module is used for analyzing the flag bit of the patch file, and the patch file is manufactured by applying the patch file manufacturing system;
the jumping module is used for jumping to a Git warehouse under the Git warehouse path of the patch file;
and the application module is used for applying the patch file under the Git warehouse.
In a fifth aspect, the present invention provides an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements the patch file making method and the patch file applying method when executing the computer program.
In a sixth aspect, the present invention provides a chip applied to an electronic device, where the chip is configured to execute the patch file making method and the patch file applying method.
In a seventh aspect, the present invention provides a chip module, which is applied to an electronic device, and includes a transceiver component and a chip, where the chip is configured to execute the patch file making method and the patch file application method.
In an eighth aspect, the present invention provides a computer-readable storage medium on which a computer program is stored, the computer program, when executed by a processor, implementing the patch file making method described above and the patch file applying method described above.
The positive progress effects of the invention are as follows:
according to the invention, the Git warehouse path of the patch file is extended to the flag bit of the patch file, so that when the patch file is applied, a user does not need to find out Git warehouses corresponding to correct patch files one by one, the patch file is automatically applied to the Git warehouse corresponding to the patch file, and the efficiency and the convenience for applying the patch file are improved.
Drawings
Fig. 1 is a first flowchart of a patch file production method according to embodiment 1 of the present invention;
fig. 2 is a second flowchart of a patch file production method according to embodiment 1 of the present invention;
fig. 3 is a flowchart of a specific example of a patch file production method according to embodiment 1 of the present invention;
fig. 4 is a flowchart of a patch file application method according to embodiment 2 of the present invention;
fig. 5 is a flowchart of a specific example of a patch file application method according to embodiment 2 of the present invention;
fig. 6 is a first configuration diagram of a patch file production system according to embodiment 3 of the present invention;
fig. 7 is a second structural diagram of a patch file production system according to embodiment 3 of the present invention;
fig. 8 is a first configuration diagram of a patch file application system according to embodiment 4 of the present invention;
fig. 9 is a second structural diagram of a patch file application system according to embodiment 4 of the present invention;
fig. 10 is a schematic structural diagram of an electronic device in embodiment 5 of the present invention.
Detailed Description
The invention is further illustrated by the following examples, which are not intended to limit the scope of the invention.
In the following, the terms "first", "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature.
It should be noted that the execution main body of the patch file making method and the patch file application method provided in this embodiment may be a separate chip, a chip module, or a UE, or may be a chip or a chip module integrated in a UE.
The patch file generation system and the patch file application system described in the embodiments may be a separate chip, a chip module, or a UE, or may be a chip or a chip module integrated in the UE. The patch file generation system and the patch file application system may include various modules/units, which may be software modules/units, or hardware modules/units, or may also be part of software modules/units, and part of hardware modules/units.
For example, for each device and product applied to or integrated in a chip, each module/unit included in the device and product may be implemented by hardware such as a circuit, or at least a part of the modules/units may be implemented by a software program running on a processor integrated in the chip, and the rest of the modules/units may be implemented by hardware such as a circuit; for each device and product applied to or integrated with the chip module, each module/unit included in the device and product may be implemented in a hardware manner such as a circuit, and different modules/units may be located in the same component (e.g., a chip, a circuit module, etc.) or different components of the chip module, or at least a part of the modules/units may be implemented in a software program running on a processor integrated inside the chip module, and the remaining part of the modules/units may be implemented in a hardware manner such as a circuit; for each device and product applied to or integrated in the UE, each module/unit included in the device and product may be implemented by hardware such as a circuit, and different modules/units may be located in the same component (e.g., a chip, a circuit module, etc.) or different components in the terminal, or at least a part of the modules/units may be implemented by a software program running on a processor integrated inside the UE, and the remaining part of the modules/units may be implemented by hardware such as a circuit.
Example 1
The present embodiment relates to a patch file manufacturing method, which is applied to a Git control system (an open source distributed version control system), and with reference to fig. 1, the patch file manufacturing method includes:
s1, obtaining a Git warehouse path of the patch file according to the pwd command.
The pwd command may display the entire path name of the current program, thereby ensuring that the correct Git warehouse path is taken where the patch file is located. The Git warehouse path is the directory address of the Git's warehouse. In the Git system, a file directory to be version-controlled is called a repository (repository), each repository can be simply understood as a directory, all files in the directory are version-managed through the Git system, and the Git system can track and record all updates occurring in the directory.
And S2, adding the Git warehouse path to a flag bit of the patch file.
When the flag bit patch file is applied, the portion of the patch file is analyzed first. Application patch file in an alternative embodiment, the flag bit includes a header or trailer of the patch file. For example: the Git warehouse path may be added to the header of the patch file. Another example is: the Git warehouse path may be added to the tail of the patch file.
In the embodiment, the Git warehouse path of the patch file is extended to the flag bit of the patch file, so that when the patch file is applied, a user does not need to find out the Git warehouses corresponding to the correct patch file one by one, the patch file is automatically applied to the Git warehouse corresponding to the patch file, and the efficiency and the convenience for applying the patch file are improved.
In an alternative embodiment, referring to fig. 2, step S1 is followed by:
s11, storing the Git warehouse path as a character string.
The step S2 comprises the following steps:
and S21, adding the character string to a flag bit of the patch file.
In an alternative embodiment, the format of the patch file is either a diff format (a file format) or a patch format (a file format).
In the embodiment, the character string is used for representing the Git warehouse path of the patch file, so that the Git warehouse path of the patch file is convenient to identify, and the application efficiency of the patch file is further improved.
In an alternative embodiment, referring to fig. 2, step S1 is preceded by:
and S10, receiving a patch file making command.
The patch file creation command includes a Git format-patch command, a gitdiff command, and the like.
A patch file in the diff format can be generated using the Git diff command, and a patch file in the patch format can be generated using the Git format-patch command.
In an optional implementation mode, the patch file making is triggered by receiving a patch file making command, and a proper patch file format is generated, so that the efficiency and the applicability of making a patch file are improved.
Fig. 3 is a specific example flowchart of the present embodiment, and refer to fig. 3:
s31, the developer inputs a Git format-patch command or a gitdiff command to start patch file production.
And S32, acquiring a Git warehouse path of the current patch file through the pwd command, and storing the Git warehouse path in a character string form.
S33, saving and writing the Git warehouse path in the form of the character string into the first line of the patch file.
And S34, writing the text content of the patch file into the patch file.
And S35, outputting the patch file in the diff format or the patch format.
Example 2
The present embodiment provides a patch file application method, which is applied to a Git control system (an open source distributed version control system), and referring to fig. 4, the patch file application method includes:
and S41, analyzing the flag bit of the patch file.
The flag bit is a portion of the patch file that is first analyzed when the patch file is applied. The patch file is obtained by applying the patch file production method of embodiment 1. On the premise of applying the patch file, the patch file needs to be known to be correctly attached to a Git warehouse, otherwise, the application of the patch file fails.
In an alternative embodiment, the flag bit comprises a header or trailer of the patch file.
S42, jumping to a Git warehouse under the Git warehouse path of the patch file.
For example, a track command (changes directory to the top of the tree, or a subdirectory theroof, i.e. switching a directory to the top of the directory tree, or one of the subdirectories) is executed, so that the Git warehouse corresponding to the patch file can be accessed.
And S43, applying the patch file under the Git warehouse.
In this embodiment, the patch file that extends the Git warehouse path of the patch file to the flag bit of the patch file is applied, and the patch file can be automatically applied to the Git warehouse corresponding to the patch file without the user finding the Git warehouse corresponding to the correct patch file one by one and directly analyzing the flag bit of the patch file, thereby improving the efficiency and convenience of applying the patch file.
In an alternative embodiment, step S41 includes:
and analyzing the zone bit of the patch file according to the key words of the character strings.
In the embodiment, the Git warehouse path of the patch file is analyzed by searching the keyword, so that the analysis efficiency is improved, and the convenience of analyzing the Git warehouse path of the patch file is improved.
In an alternative embodiment, step S41 is preceded by:
a patch file application command is received, which includes a Git apply command (an execution command), a Git am command (an execution command), and the like.
Fig. 5 is a specific example flowchart of the present embodiment, and refer to fig. 5:
s51, the user inputs a Git apply command or Git am commands to start applying the patch file.
And S52, acquiring a warehouse path of the patch file.
And S53, executing a croot command, and entering a warehouse corresponding to the patch file.
And S54, applying the patch file.
And S55, determining that the patch file is successfully applied.
Example 3
In this embodiment, a patch file generation system is provided, and referring to fig. 6, the patch file generation system includes:
and the obtaining module 61 is configured to obtain a Git warehouse path of the patch file according to the pwd command.
And a production module 62 for adding the Git warehouse path to the flag of the patch file.
The flag bit is a portion of the patch file that is analyzed first when the patch file is applied. In an alternative embodiment, referring to fig. 7, the patch file making system further includes:
and a storage module 63, configured to store the Git warehouse path as a character string.
The creating module 62 is further configured to add the character string to a flag of the patch file, where the flag is a portion of the patch file that is first parsed when the patch file is applied to the patch file. In an alternative embodiment, the flag bit comprises a header or trailer of the patch file.
In an alternative embodiment, the format of the patch file is a diff format or a patch format.
In an alternative embodiment, referring to fig. 7, the patch file making system further includes:
the first receiving module 64 is configured to receive a patch file making command, where the patch file making command includes a Git format-patch command and/or a gitdiff command.
It should be noted that, for the implementation principle and the technical effect of each module in this embodiment, reference may be made to a corresponding part in embodiment 1, and details are not described here again.
Example 4
The present embodiment provides a patch file application system, and referring to fig. 8, the patch file application system includes:
the parsing module 81 is configured to parse the flag bits of the patch file;
a skip module 82, configured to skip to a Git warehouse in the Git warehouse path of the patch file;
and an application module 83 for applying the patch file under the Git repository.
In an optional embodiment, the parsing module 81 is further configured to parse the flag of the patch file according to the keyword of the character string.
In an alternative embodiment, referring to fig. 9, the patch file application system further includes:
and a second receiving module 84, configured to receive a patch file application command, where the patch file application command includes a Git apply command and/or a Git am command.
It should be noted that, for the implementation principle and the technical effect of each module in this embodiment, reference may be made to a corresponding part in embodiment 2, and details are not described here again.
Example 5
The present embodiment provides an electronic device, and fig. 10 is a schematic block diagram of the electronic device. The electronic device includes a memory, a processor, and a computer program stored on the memory and executable on the processor, and the processor implements the patch file making method of embodiment 1 and the patch file applying method of embodiment 2 when executing the program. The electronic device 30 shown in fig. 10 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiment of the present invention.
As shown in fig. 10, the electronic device 30 may be embodied in the form of a general purpose computing device, which may be, for example, a server device. The components of the electronic device 30 may include, but are not limited to: the at least one processor 31, the at least one memory 32, and a bus 33 connecting the various system components (including the memory 32 and the processor 31).
The bus 33 includes a data bus, an address bus, and a control bus.
The memory 32 may include volatile memory, such as Random Access Memory (RAM) 321 and/or cache memory 322, and may further include Read Only Memory (ROM) 323.
Memory 32 may also include a program/utility 325 having a set (at least one) of program modules 324, such program modules 324 including, but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which, or some combination thereof, may comprise an implementation of a network environment.
The processor 31 executes various functional applications and data processing, such as the patch file making method of embodiment 1 and the patch file applying method of embodiment 2 of the present invention, by running the computer program stored in the memory 32.
The electronic device 30 may also communicate with one or more external devices 34 (e.g., keyboard, pointing device, etc.). Such communication may be through input/output (I/O) interfaces 35. Also, model-generating device 30 may also communicate with one or more networks (e.g., a Local Area Network (LAN), a Wide Area Network (WAN), and/or a public network, such as the Internet) via network adapter 36. As shown in FIG. 10, network adapter 36 communicates with the other modules of model-generated device 30 via bus 33. It should be understood that although not shown in the figures, other hardware and/or software modules may be used in conjunction with the model-generating device 30, including but not limited to: microcode, device drivers, redundant processors, external disk drive arrays, RAID (disk array) systems, tape drives, and data backup storage systems, etc.
It should be noted that although in the above detailed description several units/modules or sub-units/modules of the electronic device are mentioned, such a division is merely exemplary and not mandatory. Indeed, the features and functionality of two or more of the units/modules described above may be embodied in one unit/module according to embodiments of the invention. Conversely, the features and functions of one unit/module described above may be further divided into embodiments by a plurality of units/modules.
Example 6
The present embodiment provides a computer-readable storage medium on which a computer program is stored, the program implementing the patch file making method of embodiment 1 and the patch file applying method of embodiment 2 when executed by a processor.
More specific examples, among others, that the readable storage medium may employ may include, but are not limited to: a portable disk, a hard disk, random access memory, read only memory, erasable programmable read only memory, optical storage device, magnetic storage device, or any suitable combination of the foregoing.
In a possible embodiment, the present invention can also be implemented in the form of a program product including program code for causing a terminal device to execute a patch file making method implementing embodiment 1 and a patch file applying method implementing embodiment 2 when the program product is run on the terminal device.
Where program code for carrying out the invention is written in any combination of one or more programming languages, the program code may execute entirely on the user's device, partly on the user's device, as a stand-alone software package, partly on the user's device, partly on a remote device or entirely on the remote device.
While specific embodiments of the invention have been described above, it will be understood by those skilled in the art that this is by way of example only, and that the scope of the invention is defined by the appended claims. Various changes and modifications to these embodiments may be made by those skilled in the art without departing from the spirit and scope of the invention, and these changes and modifications are within the scope of the invention.

Claims (12)

1. A patch file production method is characterized by comprising the following steps:
acquiring a Git warehouse path of the patch file according to the pwd command;
and adding the Git warehouse path to a flag bit of the patch file, wherein the flag bit is the part of the patch file which is firstly analyzed when the patch file is applied with the patch file.
2. The patch file making method according to claim 1, wherein said step of obtaining the Git warehouse path of the patch file according to the pwd command comprises:
saving the Git warehouse path as a string;
the step of adding the Git warehouse path to the flag bit of the patch file comprises:
adding the character string to a flag bit of the patch file;
and/or the presence of a gas in the gas,
the flag bit comprises the head or the tail of the patch file;
and/or the presence of a gas in the gas,
the format of the patch file is a diff format or a patch format.
3. The patch file making method according to claim 1, wherein the step of obtaining the Git warehouse path of the patch file according to the pwd command comprises:
receiving a patch file making command, wherein the patch file making command comprises a gitform-patch command and/or a gitdiff command.
4. A patch file application method is characterized by comprising the following steps:
analyzing a flag bit of a patch file, wherein the patch file is manufactured by applying the patch file manufacturing method of any one of claims 1 to 3;
jumping to a Git warehouse under the Git warehouse path of the patch file;
and applying the patch file under the Git warehouse.
5. The patch file application method as claimed in claim 4, wherein the step of parsing the flag bit of the patch file comprises:
and analyzing the zone bit of the patch file according to the key words of the character string.
6. The patch file application method according to claim 4, wherein the step of parsing the flag bit of the patch file comprises:
receiving an application patch file application command, wherein the application patch file application command comprises a Git apply command and/or a Git am command.
7. A patch file production system, comprising:
the acquisition module is used for acquiring a Git warehouse path of the patch file according to the pwd command;
and the manufacturing module is used for adding the Git warehouse path to a flag bit of the patch file, wherein the flag bit is the part of the patch file which is firstly analyzed when the patch file is applied to the patch file.
8. A patch file application system, comprising:
the analysis module is used for analyzing the flag bit of the patch file, and the patch file is manufactured by the patch file manufacturing system of the application right claim 7;
the jumping module is used for jumping to a Git warehouse under the Git warehouse path of the patch file;
and the application module is used for applying the patch file under the Git warehouse.
9. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor implements the patch file making method of any one of claims 1 to 3 and the patch file applying method of any one of claims 4 to 6 when executing the computer program.
10. A chip applied to an electronic device, wherein the chip is configured to perform the patch file making method according to any one of claims 1 to 3 and the patch file applying method according to any one of claims 4 to 6.
11. A chip module applied to an electronic device, comprising a transceiver component and a chip, wherein the chip is used for executing the patch file making method of any one of claims 1 to 3 and the patch file application method of any one of claims 4 to 6.
12. A computer-readable storage medium on which a computer program is stored, the computer program, when being executed by a processor, implementing the patch file making method according to any one of claims 1 to 3 and the patch file applying method according to any one of claims 4 to 6.
CN202211204222.6A 2022-09-29 2022-09-29 Patch file making and application method, system, electronic equipment and storage medium Pending CN115495143A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202211204222.6A CN115495143A (en) 2022-09-29 2022-09-29 Patch file making and application method, system, electronic equipment and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202211204222.6A CN115495143A (en) 2022-09-29 2022-09-29 Patch file making and application method, system, electronic equipment and storage medium

Publications (1)

Publication Number Publication Date
CN115495143A true CN115495143A (en) 2022-12-20

Family

ID=84471878

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202211204222.6A Pending CN115495143A (en) 2022-09-29 2022-09-29 Patch file making and application method, system, electronic equipment and storage medium

Country Status (1)

Country Link
CN (1) CN115495143A (en)

Similar Documents

Publication Publication Date Title
CN108932122B (en) Interface document generation method, device, computer equipment and storage medium
US8630841B2 (en) Regular expression word verification
US8626786B2 (en) Dynamic language checking
US8782609B2 (en) Test failure bucketing
JP4150060B2 (en) Method for loading a resource module in a computer system
US10621211B2 (en) Language tag management on international data storage
US9098500B1 (en) Revision history storage and maintenance
CN112000398B (en) Method and device for determining bottom layer interface call link, computer equipment and medium
CN104346153A (en) Method and system for translating text information of application programs
US8316006B2 (en) Creating an ontology using an online encyclopedia and tag cloud
CN109471851B (en) Data processing method, device, server and storage medium
US20180203844A1 (en) Detection of meaningful changes in content
CN110633219B (en) Page test method and device, storage medium and electronic equipment
US20170169069A1 (en) Data integrity checking in a distributed filesystem using object versioning
US20160124795A1 (en) Evaluation method and apparatus
CN110990346A (en) File data processing method, device, equipment and storage medium based on block chain
US20040237046A1 (en) Unicode transitional code point database
CN113094625B (en) Page element positioning method and device, electronic equipment and storage medium
CN111984659B (en) Data updating method, device, computer equipment and storage medium
CN112632425A (en) Method, device, equipment and storage medium for generating offline resource file
CN111177089B (en) Log processing code generation method and device, computer system and storage medium
CN115495143A (en) Patch file making and application method, system, electronic equipment and storage medium
US20050289525A1 (en) Extensible command line parsing
US11704099B1 (en) Discovering matching code segments according to index and comparative similarity
US10942934B2 (en) Non-transitory computer-readable recording medium, encoded data searching method, and encoded data searching apparatus

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