| OLD | NEW |
| 1 # git-cl | 1 # git-cl |
| 2 | 2 |
| 3 The git-cl README describes the git-cl command set. This document describes how | 3 The git-cl README describes the git-cl command set. This document describes how |
| 4 code review and git work together in general, intended for people familiar with | 4 code review and git work together in general, intended for people familiar with |
| 5 git but unfamiliar with the code review process supported by Rietveld and | 5 git but unfamiliar with the code review process supported by Rietveld and |
| 6 Gerrit. | 6 Gerrit. |
| 7 | 7 |
| 8 | 8 |
| 9 ## Reitveld concepts and terms | 9 ## Reitveld concepts and terms |
| 10 | 10 |
| (...skipping 79 matching lines...) Expand 10 before | Expand all | Expand 10 after Loading... |
| 90 | 90 |
| 91 O---A---B---C | 91 O---A---B---C |
| 92 \ \ \ | 92 \ \ \ |
| 93 A'--B'--C' | 93 A'--B'--C' |
| 94 | 94 |
| 95 Which is ugly, but it accurately tracks the real history of your work, can be | 95 Which is ugly, but it accurately tracks the real history of your work, can be |
| 96 thrown away at the end by committing A+A' as a single `squash` commit. | 96 thrown away at the end by committing A+A' as a single `squash` commit. |
| 97 | 97 |
| 98 In practice, this comes up pretty rarely. Suggestions for better workflows are | 98 In practice, this comes up pretty rarely. Suggestions for better workflows are |
| 99 welcome. | 99 welcome. |
| 100 |
| 101 ## Bash auto complition |
| 102 |
| 103 1. Ensure that your base git commands are autocompleted |
| 104 [doc](https://git-scm.com/book/en/v1/Git-Basics-Tips-and-Tricks). |
| 105 2. Add this to your .bashrc: |
| 106 |
| 107 # The next line enables bash completion for git cl. |
| 108 if [ -f "$HOME/bin/depot_tools/git_cl_completion.sh" ]; then |
| 109 . "$HOME/bin/depot_tools/git_cl_completion.sh" |
| 110 fi |
| 111 |
| 112 3. Profit. |
| OLD | NEW |