summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKarl Williamson <public@khwilliamson.com>2010-08-01 12:50:38 -0600
committerJesse Vincent <jesse@bestpractical.com>2010-08-09 11:08:27 -0700
commit2be70973e973445babb19dda3b444b93bdb23b20 (patch)
treea0524a2c2c8852d654742bdb54dc69da4b604620
parent456a14466223069969e460f6708b6dfbf05a65e4 (diff)
downloadperl-2be70973e973445babb19dda3b444b93bdb23b20.tar.gz
perlrepository.pod: Elaborate -a, -m
-rw-r--r--pod/perlrepository.pod12
1 files changed, 12 insertions, 0 deletions
diff --git a/pod/perlrepository.pod b/pod/perlrepository.pod
index bf7e51138d..bc0c192d27 100644
--- a/pod/perlrepository.pod
+++ b/pod/perlrepository.pod
@@ -342,6 +342,18 @@ Now commit your change locally:
Created commit 6196c1d: Rename Leon Brocard to Orange Brocard
1 files changed, 1 insertions(+), 1 deletions(-)
+The C<-a> option is used to include all files that git tracks that you have
+changed. If at this time, you only want to commit some of the files you have
+worked on, you can omit the C<-a> and use the command C<S<git add I<FILE ...>>>
+before doing the commit. C<S<git add --interactive>> allows you to even just
+commit portions of files instead of all the changes in them.
+
+The C<-m> option is used to specify the commit message. If you omit it, git
+will open a text editor for you to compose the message interactively. This
+is useful when the changes are more complex than the sample given here, and,
+depending on the editor, to know that the first line of the commit message
+doesn't exceed the 50 character legal maximum.
+
You can examine your last commit with:
% git show HEAD