Open main menu

Changes

Git asynchronous development

166 bytes added, 14:19, 25 June 2013
[http://git-scm.com/book/en/Git-Basics-Viewing-the-Commit-History This section is prepared from this site].
Export both commit message and change to last commit to file
git log -p -1
git log -p -1 > nmrpipe2_log
Using a GUI to Visualize History. If you like to use a more graphical tool to visualize your commit history, you may want to take a look at a Tcl/Tk program called gitk that is distributed with Git. Gitk is basically a visual git log tool, and it accepts nearly all the filtering options that git log does. Type gitk on the command line in your project.
gitk
To find out, how long we would like to go back, we use the log
git log
We would like change the commit message two commits ago with commit hash sha1 of ('''^^833b91e6064cc8175ad741757ada25edd52c2cce''') git rebase -i HEAD^^833b91e6064cc8175ad741757ada25edd52c2cce~1 git add -u # To add changes from all tracked filesInstead of 'sha1' you can use 'HEAD~N', where N is the number of commits before 'HEAD' git commit rebase -C i HEAD # reuse ~2 Now mark the commit thatones you want to amend with reword '''r'''s there(replace pick). Now save and exit editor. Omit this option if <br>In the next editor, you want can then write the new message. Save and exit editor. Now create your patch, comparing to change that toothe sr branch git rebase -format-continuepatch sr
== See also ==
Trusted, Bureaucrats
1,382

edits