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

[PATCH 02/12] Utilise the new 'p4_read_pipe_lines' command

From
AKAnand Kumria <wildfire@progsoc.org>
Date
Aug 10, 2008, 18:26 UTC
Message-ID
<1218392795-4084-3-git-send-email-wildfire@progsoc.org>
In-Reply-To
<1218392795-4084-2-git-send-email-wildfire@progsoc.org>
 Now that we have the new command, we can utilise it and then
 eventually, isolate any changes required to the one place.
Signed-off-by: Anand Kumria <wildfire@progsoc.org>
---
 contrib/fast-import/git-p4 |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/contrib/fast-import/git-p4 b/contrib/fast-import/git-p4
index fc2a60d..3deaa42 100755
--- a/contrib/fast-import/git-p4
+++ b/contrib/fast-import/git-p4
@@ -371,7 +371,7 @@ def originP4BranchesExist():
 
 def p4ChangesForPaths(depotPaths, changeRange):
     assert depotPaths
-    output = read_pipe_lines("p4 changes " + ' '.join (["%s...%s" % (p, changeRange)
+    output = p4_read_pipe_lines("changes " + ' '.join (["%s...%s" % (p, changeRange)
                                                         for p in depotPaths]))
 
     changes = []
@@ -519,7 +519,7 @@ class P4Submit(Command):
         # remove lines in the Files section that show changes to files outside the depot path we're committing into
         template = ""
         inFilesSection = False
-        for line in read_pipe_lines("p4 change -o"):
+        for line in p4_read_pipe_lines("change -o"):
             if line.endswith("\r\n"):
                 line = line[:-2] + "\n"
             if inFilesSection:
-- 
1.5.6.3
Previous: Anand KumriaNext: Anand Kumria
Message 3 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.