Skip to content

Commit 2e1fb6c

Browse files
committed
Changed word (write to wrote) to fix typo in section 9.1 regarding p4
1 parent b8a399a commit 2e1fb6c

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

book/09-git-and-other-scms/sections/client-p4.asc

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -480,7 +480,7 @@ Files:
480480

481481
This is mostly the same content you'd see by running `p4 submit`, except the stuff at the end which git-p4 has helpfully included.
482482
Git-p4 tries to honor your Git and Perforce settings individually when it has to provide a name for a commit or changeset, but in some cases you want to override it.
483-
For example, if the Git commit you're importing was written by a contributor who doesn't have a Perforce user account, you may still want the resulting changeset to look like they write it (and not you).
483+
For example, if the Git commit you're importing was written by a contributor who doesn't have a Perforce user account, you may still want the resulting changeset to look like they wrote it (and not you).
484484

485485
Git-p4 has helpfully imported the message from the Git commit as the content for this Perforce changeset, so all we have to do is save and quit, twice (once for each commit).
486486
The resulting shell output will look something like this:

0 commit comments

Comments
 (0)