diff options
| author | Yves Orton <demerphq@camel.booking.com> | 2008-12-20 15:12:46 +0100 |
|---|---|---|
| committer | Yves Orton <demerphq@camel.booking.com> | 2008-12-20 15:12:46 +0100 |
| commit | 23f8d33e693e28440faad53924ec93ba0460cfc9 (patch) | |
| tree | fbcfa3621b4aa55e6557c3e7ba2e3a29552fc7dd /pod/perlrepository.pod | |
| parent | 7f6effc75c40e04415028b3c68e8cb6a07f3f21d (diff) | |
| download | perl-23f8d33e693e28440faad53924ec93ba0460cfc9.tar.gz | |
trim trailing spaces
Diffstat (limited to 'pod/perlrepository.pod')
| -rw-r--r-- | pod/perlrepository.pod | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/pod/perlrepository.pod b/pod/perlrepository.pod index 35c42623b7..d790099177 100644 --- a/pod/perlrepository.pod +++ b/pod/perlrepository.pod @@ -98,7 +98,7 @@ You can see recent commits: % git log -And pull new changes from the repository, and update your local repository +And pull new changes from the repository, and update your local repository (must be clean first) % git pull @@ -136,10 +136,10 @@ The most common git command you will use will probably be % git status -This command will produce as output a description of the current state of the +This command will produce as output a description of the current state of the repository, including modified files and unignored untracked files, and in addition -it will show things like what files have been staged for the next commit, -and usually some useful information about how to change things. For instance the +it will show things like what files have been staged for the next commit, +and usually some useful information about how to change things. For instance the following: $ git status @@ -166,7 +166,7 @@ that there were further changes in the working directory not yet staged. It also shows that there was an untracked file in the working directory, and as you can see shows how to change all of this. It also shows that there is one commit on the working branch C<blead> which has not been pushed to the -C<origin> remote yet. B<NOTE>: that this output is also what you see as a +C<origin> remote yet. B<NOTE>: that this output is also what you see as a template if you do not provide a message to c<git commit>. Assuming we commit all the mentioned changes above: @@ -188,7 +188,7 @@ We can re-run git status and see something like this: nothing added to commit but untracked files present (use "git add" to track) -When in doubt, before you do anything else, check your status and read it +When in doubt, before you do anything else, check your status and read it carefully, many questions are answered directly by the git status output. =head1 SUBMITTING A PATCH @@ -213,7 +213,7 @@ Now that we have everything up to date, we need to create a temporary new branch for these changes and switch into it: % git checkout -b orange - + which is the short form of % git branch orange |