Put some documentation in about the parameters that have been added
Signed-off-by: Anand Kumria <wildfire@progsoc.org> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Anand Kumria committed
Aug 10, 2008 at 19:26 UTC
b87a659635f40b5301c6b18fa5e22c72ca79b830
1 file changed
+32
contrib/fast-import/git-p4.txt
+32
@@ -131,6 +131,38 @@ Example
131
Configuration parameters
132
========================
133
134
+git-p4.user ($P4USER)
135
+
136
+Allows you to specify the username to use to connect to the Perforce repository.
137
+
138
+ git config [--global] git-p4.user public
139
+
140
+git-p4.password ($P4PASS)
141
+
142
+Allows you to specify the password to use to connect to the Perforce repository.
143
+Warning this password will be visible on the command-line invocation of the p4 binary.
144
+
145
+ git config [--global] git-p4.password public1234
146
+
147
+git-p4.port ($P4PORT)
148
+
149
+Specify the port to be used to contact the Perforce server. As this will be passed
150
+directly to the p4 binary, it may be in the format host:port as well.
151
+
152
+ git config [--global] git-p4.port codes.zimbra.com:2666
153
+
154
+git-p4.host ($P4HOST)
155
+
156
+Specify the host to contact for a Perforce repository.
157
+
158
+ git config [--global] git-p4.host perforce.example.com
159
+
160
+git-p4.client ($P4CLIENT)
161
+
162
+Specify the client name to use
163
+
164
+ git config [--global] git-p4.client public-view
165
+
166
git-p4.syncFromOrigin
167
168
A useful setup may be that you have a periodically updated git repository