summaryrefslogtreecommitdiff
path: root/Porting
diff options
context:
space:
mode:
authorGurusamy Sarathy <gsar@cpan.org>2002-09-05 06:28:36 +0000
committerGurusamy Sarathy <gsar@cpan.org>2002-09-05 06:28:36 +0000
commit83d057904fcf43ccbeee0b8e23d13ba528a6cb6a (patch)
tree9d1b6109a3281b2f386052a12fecee9089bd111d /Porting
parent04c4667fcfa7b046ac3562fbae400760de2b0542 (diff)
downloadperl-83d057904fcf43ccbeee0b8e23d13ba528a6cb6a.tar.gz
document setting the email address
p4raw-id: //depot/perl@17849
Diffstat (limited to 'Porting')
-rw-r--r--Porting/repository.pod9
1 files changed, 5 insertions, 4 deletions
diff --git a/Porting/repository.pod b/Porting/repository.pod
index db2e1842b1..5cc2d993fc 100644
--- a/Porting/repository.pod
+++ b/Porting/repository.pod
@@ -199,7 +199,7 @@ the section above on the B<-L 1666:127.0.0.1:1666> option to ssh.
The value of this is the name by which Perforce knows your
host's workspace. You need to pick a name (normally, your
-Perforce username, a dash, and your hostname)
+Perforce username, a dash, and your host's short name)
when you first start using the perl repository and then
stick with it.
@@ -258,9 +258,10 @@ The C<p4 users> command lists all currently known users.
Once these three environment variables are set, you can use the
perforce p4 client exactly as described in its documentation.
After setting these variables and connecting to the repository
-for the first time, you should use the C<p4 user> and
-C<p4 client> commands to tell perforce the details of your
-new username and your new client workspace specifications.
+for the first time, you should use the C<p4 user> command to
+set a valid email address for yourself. Also use the C<p4 client>
+command to specify your workspace specifications for each
+individual client from which you will interact with the repository.
=head1 Ending a Repository Session