git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH 11/12] Put some documentation in about the parameters that have been added

From
AKAnand Kumria <wildfire@progsoc.org>
Date
Aug 10, 2008, 18:26 UTC
Message-ID
<1218392795-4084-12-git-send-email-wildfire@progsoc.org>
In-Reply-To
<1218392795-4084-11-git-send-email-wildfire@progsoc.org>
Signed-off-by: Anand Kumria <wildfire@progsoc.org>
---
 contrib/fast-import/git-p4.txt |   32 ++++++++++++++++++++++++++++++++
 1 files changed, 32 insertions(+), 0 deletions(-)
diff --git a/contrib/fast-import/git-p4.txt b/contrib/fast-import/git-p4.txt
index 0896abb..79a22e9 100644
--- a/contrib/fast-import/git-p4.txt
+++ b/contrib/fast-import/git-p4.txt
@@ -131,6 +131,38 @@ Example
 Configuration parameters
 ========================
 
+git-p4.user ($P4USER)
+
+Allows you to specify the username to use to connect to the Perforce repository.
+
+  git config [--global] git-p4.user public
+
+git-p4.password ($P4PASS)
+
+Allows you to specify the password to use to connect to the Perforce repository.
+Warning this password will be visible on the command-line invocation of the p4 binary.
+
+  git config [--global] git-p4.password public1234
+
+git-p4.port ($P4PORT)
+
+Specify the port to be used to contact the Perforce server. As this will be passed
+directly to the p4 binary, it may be in the format host:port as well.
+
+  git config [--global] git-p4.port codes.zimbra.com:2666
+
+git-p4.host ($P4HOST)
+
+Specify the host to contact for a Perforce repository.
+
+  git config [--global] git-p4.host perforce.example.com
+
+git-p4.client ($P4CLIENT)
+
+Specify the client name to use
+
+  git config [--global] git-p4.client public-view
+
 git-p4.syncFromOrigin
 
 A useful setup may be that you have a periodically updated git repository

-- 
1.5.6.3
Previous: Anand KumriaNext: Anand Kumria
Message 12 of 16 in “Allow users to access Perforce repositories requiring authentication”
  1. 00/12 Allow users to access Perforce repositories requiring authenticationAnand Kumria, Aug 10, 2008
  2. 01/12 Create a specific version of the read_pipe_lines command for p4 invocationsAnand Kumria, Aug 10, 2008
  3. 02/12 Utilise the new 'p4_read_pipe_lines' commandAnand Kumria, Aug 10, 2008
  4. 03/12 Have a command that specifically invokes 'p4' (via system)Anand Kumria, Aug 10, 2008
  5. 04/12 Utilise the new 'p4_system' function.Anand Kumria, Aug 10, 2008
  6. 05/12 Add a single command that will be used to construct the 'p4' commandAnand Kumria, Aug 10, 2008
  7. 06/12 If we are in verbose mode, output what we are about to run (or return)Anand Kumria, Aug 10, 2008
  8. 07/12 Switch to using 'p4_build_cmd'Anand Kumria, Aug 10, 2008
  9. 08/12 If the user has configured various parameters, use them.Anand Kumria, Aug 10, 2008
  10. 09/12 Consistently use 'git-p4' for the configuration entriesAnand Kumria, Aug 10, 2008
  11. 10/12 Move git-p4.syncFromOrigin into a configuration parameters sectionAnand Kumria, Aug 10, 2008
  12. 11/12 Put some documentation in about the parameters that have been addedAnand Kumria, Aug 10, 2008
  13. 12/12 Put in the two other configuration elements found in the sourceAnand Kumria, Aug 10, 2008
  14. Simon HausmannAug 13, 2008
  15. Tor Arvid LundAug 14, 2008
  16. Anand KumriaAug 14, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.