summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorVincent Pit <perl@profvince.com>2008-12-21 20:34:23 +0100
committerVincent Pit <perl@profvince.com>2008-12-21 20:34:23 +0100
commitf6c12373efa87e4286a97122c0ea72922ef8bcec (patch)
treec7b1cd9e0691b8beb2d3f420126969b8083a0d93
parentb0d365353ceae5c23a4b57375afb739159cefdfc (diff)
downloadperl-f6c12373efa87e4286a97122c0ea72922ef8bcec.tar.gz
Document how commiters can keep 'origin' as a git remote and push with another ssh remote.
-rw-r--r--pod/perlrepository.pod11
1 files changed, 11 insertions, 0 deletions
diff --git a/pod/perlrepository.pod b/pod/perlrepository.pod
index 946bb55bf4..7b1b6191fb 100644
--- a/pod/perlrepository.pod
+++ b/pod/perlrepository.pod
@@ -72,6 +72,17 @@ You can also set up your user name and e-mail address. For example
% git config user.name "Leon Brocard"
% git config user.email acme@astray.com
+It is also possible to keep C<origin> as a git remote, and add a new remote for ssh access:
+
+ % git remote add camel user@camel:/gitroot/perl.git
+
+This allows you to update your local repository by pulling from C<origin>, which is faster and doesn't require you to authentify, and to push your changes back with the C<camel> remote:
+
+ % git fetch camel
+ % git push camel
+
+The C<fetch> command just updates the C<camel> refs, as the objects themselves should have been fetched when pulling from C<origin>.
+
=head1 OVERVIEW OF THE REPOSITORY
Once you have changed into the repository directory, you can inspect it.