Lines Matching full:commit
86 the +HEAD+ of the repository (usually the latest commit) is well over 100
136 * Include relevant links, Git commit hashes and CVE numbers.
277 commit make sure you have configured Git correctly. You need to at least set
300 $ git commit -m "statx01: Add new test for statx syscall"
304 file. It is good practice to commit early and often. Later on we will do a
305 Git-rebase, which allows us to clean up the commit history. So don't worry
306 about how presentable your commit log is for now. Also don't hesitate to
820 will allow you to reshape your commit history without fear.
823 our commit history. In its current form the test only really needs a single
824 commit, but if you have been using Git correctly then you should have
825 many. The main reason we want to compress it to a single commit, is to make
828 test description in the code will probably make the commit message redundant.
830 Anyway, as an example, we shall look at my personal commit history from this
832 repository. First lets look at the commit history since we branched from
861 As usual my commit history is starting to look like a bit of mess! There is
862 even a commit in there which should not be in the this branch (Remove old API
869 +tutorial:+ into the bottom commit.
877 This begins an interactive 'rebase' where commit 5ca6427b78 is the earliest
878 commit we want to edit. The +^+ symbol after the commit hash, specifies the
879 commit before this one. The interactive 'rebase' command takes the last commit
907 The last commit from Git-log is shown at the top. The left hand column
908 contains the commands we want to run on each commit. +pick+ just means we
909 re-apply the commit as-is. We can reorder the lines to apply the commits in a
915 we pick a point in the commit history, undo all those commits before that
920 allows you to edit a single commit's message. The 'fixup' command 'squashes' a
921 commit into the commit above/preceding it, merging the two commits into
922 one. The commit which has +fixup+ applied has its commit message deleted. If
923 you think a commit might have something useful in its message then you can use
946 after 5ca62 at the top. A new commit will then be created with the amalgamated
951 I could now do the same for the commits to the +statx+ test, making the commit
956 apart a commit. It is also possible using Git-rebase by marking a line with
957 +edit+. This will pause Git just after replaying the marked commit. You can
958 then use a 'soft' Git-reset to bring the selected commit's changes back into
962 You can also use +edit+ and +git commit --amend+ together to change a commit
966 So now that the commit history has been cleaned up, we need to submit a patch
1014 The first argument +-1+ specifies we want one commit from fd3cc8596
1015 onwards. If we wanted this commit and the one after it we could specify +-2+
