git diff

area file to warehouse area $ git commit[File1][File2]...-M[Message]# commit workspace changes since last commit, go directly to warehouse area $ git commit-a # commit when displaying all diff information $ git commit -v# Use a new commit, Override last Commit # If the code does not have any new changes, it is used to

submitting comments.Prompt>Git log -- pretty = onelineShow Number of changed rowsPrompt>Git log -- statDisplay the name and status of the modified FilePrompt>Git log -- name-statusDisplay the differences between the current working directory tree and the temporary storage IntervalPrompt>Git diffDisplay the differences

Git Common commands and git Common commands===== Git Common commands ======= 1.Git documentation ===Git Chinese Document viewing address: http://git.oschina.net/progit/=== 2.Git basic commands ===

code that is downloaded from the server and the local code. or a branching merge.For example: currently on the Master branch, if you want to merge branch dev onto master, git merge devNote: git merge nov/eclair_eocket (is to merge the Eclair_eocket branch of the server git library onto a local branch)Git rebase nov/ec

: file2 newfile: file3Now that you're ready for commit, you can use the git diff command plus the –cached parameter to see which files in the cache have been modified. After entering the Git diff–cached interface, you need to enter Q to exit:$gitdiff--cachedWithout the –cached parameter,

] Deletes the remote branch.git diff:git diff--name-only 73a79c 2d49d2 see the list of files that have been changed in the middle of two versionsGit diff:workspace and index file.git diff head:workspace and Commintgit diff--cached:index file and commitgit fetch:git fetch [Remote-name] retrieves all the commit information from the remote repositorygit clone:git cl

ArticleDirectory 1. Concept 2. Git Configuration 3. View commands 3. Local Database Operations 4. Remote database operations 5. View File modifications (diff) 6. Reset and revert) 7. Create a tag) 8, Miscellaneous Because git (GitHub) is used in the project, and git commands have

conflictCause: Two people change the same location content of the same file at the same timeWORKAROUND: When submitting a file that creates this conflict, we use the file diff comparison to view the location of the two file content conflicts manually and then push to the server.12. Branch Management PolicyGit has made it easier for us to create and merge branches, while the version is blooming and branching everywhere, making it easy for first-time u

minutes or weeks (Yes, I ran for more than a week ). after that, you should have a git repo with the upstream SVN repo ready for use. available Git SVN info Check the svn repo information corresponding to this git repo. Now you can use Git Branch Check the current git

"[Email address]" third, add/delete files # Add the specified file to staging area $ git add [file1] [file2] ... # Add the specified directory to staging area, including subdirectories $ git add [dir] # to add all files of the current directory to staging area $ git Add. # before adding each change, will ask to confirm # for multiple changes to the same f

local git push-u Origin master uses git status to view file status Git Status View commit log git log # view commit info git log--pretty=Oneline # Displaying commit information in a neat single-line git branch

put this deletion into staging area $ git rm [file1] [file2 ] ... # Stop tracking the specified file, but the file will remain in the workspace $ git rm--cached [file] # Renaming files and put this renaming into staging area $ git mv [file-original] [ File-renamed] Iv. Code Submission # Submit staging Area to warehouse area [message] # Submit Staging ar

may not exceed 1MB, so we should be able to update the program at a very low cost as long as we can have a diff of two version codes. As a result, Larry wall developed a tool: patch. It can be updated according to a diff file. But in git, it's not necessary to use diff and patch directly to make patches, which is both

, fuller output log in different formgit log--pretty=format: "%h-%an,%ar:%s" is output in the specified format.For additional options on--pretty and the specific format format, refer to the section pretty format in git log--help.git log--follow file.cThis feature is interesting, especially when FILE.C is moved.Usually we move a file to a directory. If you do this, git log cannot display the records before t

staging area, including subdirectories $ git add[dir]# Add all files of the current directory to staging area $ git add . # Delete the workspace file and put this deletion into staging area $ git rm [file1] [file2] . . # Stop tracking the specified file, but the file will remain in the workspace $ git rm --cached [Fi

deletion into staging area $ git rm [file1] [file2] . . # Stop tracking the specified file, but the file will remain in the workspace $ git rm --cached [File]# Renaming files and put this name into staging area $ git mv [File- Original] [file-renamed] Iv. Code Submission # Commit staging Area to warehouse area $

storage zone. $ Git RM [file1] [file2]... # Rename the file and place it in the temporary storage area $ Git MV [file-original] [file-renamed] 4. Code submission # Submit the temporary storage area to the warehouse area $ Git commit-M [Message] # Submit a specified file for the temporary storage area to the warehouse area $