diff options
| author | Yawar Amin <yawar.amin@gmail.com> | 2010-10-23 20:24:30 -0400 |
|---|---|---|
| committer | Owen W. Taylor <otaylor@fishsoup.net> | 2012-02-04 14:46:28 -0500 |
| commit | d5d6ca538cd4b7a1b4aadea67480b5bed05f37c4 (patch) | |
| tree | 670b013ddc73d4852b26205a2fd2df77ca1be702 /git-bz.txt | |
| parent | 70cf6bf25b3dec821a4f4f6960f5b94216e064c9 (diff) | |
| download | git-bz-d5d6ca538cd4b7a1b4aadea67480b5bed05f37c4.tar.gz | |
Spelling correction
Diffstat (limited to 'git-bz.txt')
| -rw-r--r-- | git-bz.txt | 4 |
1 files changed, 2 insertions, 2 deletions
@@ -23,7 +23,7 @@ DESCRIPTION git-bz is a tool for integrating the Git command line with the Bugzilla bug-tracking system. Operations such as attaching patches to bugs, applying patches in bugs to your current tree, and closing bugs once -you've pushed the fixes publically can be done completely from the +you've pushed the fixes publicly can be done completely from the command line without having to go to your web browser. Authentication for git-bz is done by reading the cookies for the @@ -112,7 +112,7 @@ add-url For each specified commit, rewrite the commit message to add a reference to the given bug. You should only do this if you haven't -already pushed the commit publically. You won't need this very often, +already pushed the commit publicly. You won't need this very often, since 'git bz file' and 'git bz attach' do this automatically. It might be useful if you want to record the bug information but don't want to attach it immediately. |