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

[PATCH 10/12] Move git-p4.syncFromOrigin into a configuration parameters section

From
AKAnand Kumria <wildfire@progsoc.org>
Date
Aug 10, 2008, 18:26 UTC
Message-ID
<1218392795-4084-11-git-send-email-wildfire@progsoc.org>
In-Reply-To
<1218392795-4084-10-git-send-email-wildfire@progsoc.org>
Signed-off-by: Anand Kumria <wildfire@progsoc.org>
---
 contrib/fast-import/git-p4.txt |   28 ++++++++++++++++------------
 1 files changed, 16 insertions(+), 12 deletions(-)
diff --git a/contrib/fast-import/git-p4.txt b/contrib/fast-import/git-p4.txt
index b16a838..0896abb 100644
--- a/contrib/fast-import/git-p4.txt
+++ b/contrib/fast-import/git-p4.txt
@@ -63,18 +63,6 @@ It is recommended to run 'git repack -a -d -f' from time to time when using
 incremental imports to optimally combine the individual git packs that each
 incremental import creates through the use of git-fast-import.
 
-
-A useful setup may be that you have a periodically updated git repository
-somewhere that contains a complete import of a Perforce project. That git
-repository can be used to clone the working repository from and one would
-import from Perforce directly after cloning using git-p4. If the connection to
-the Perforce server is slow and the working repository hasn't been synced for a
-while it may be desirable to fetch changes from the origin git repository using
-the efficient git protocol. git-p4 supports this setup by calling "git fetch origin"
-by default if there is an origin branch. You can disable this using
-
-  git config git-p4.syncFromOrigin false
-
 Updating
 ========
 
@@ -140,6 +128,22 @@ Example
   git-p4 rebase
 
 
+Configuration parameters
+========================
+
+git-p4.syncFromOrigin
+
+A useful setup may be that you have a periodically updated git repository
+somewhere that contains a complete import of a Perforce project. That git
+repository can be used to clone the working repository from and one would
+import from Perforce directly after cloning using git-p4. If the connection to
+the Perforce server is slow and the working repository hasn't been synced for a
+while it may be desirable to fetch changes from the origin git repository using
+the efficient git protocol. git-p4 supports this setup by calling "git fetch origin"
+by default if there is an origin branch. You can disable this using:
+
+  git config [--global] git-p4.syncFromOrigin false
+
 Implementation Details...
 =========================
 
-- 
1.5.6.3
Previous: Anand KumriaNext: Anand Kumria
Message 11 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.