From: Scott Lamb <slamb@slamb.org>
To: git@vger.kernel.org, Junio C Hamano <junkio@cox.net>
Cc: Scott Lamb <slamb@slamb.org>
Subject: [PATCH 4/4] git-p4import: partial history
Date: Sat, 2 Jun 2007 20:58:46 -0700 [thread overview]
Message-ID: <11808431401213-git-send-email-slamb@slamb.org> (raw)
In-Reply-To: <11808431364066-git-send-email-slamb@slamb.org>
Allow importing partial history, which is quicker and may be necessary with
a low Perforce MaxScanRows limit.
Signed-off-by: Scott Lamb <slamb@slamb.org>
---
Documentation/git-p4import.txt | 6 ++++++
git-p4import.py | 14 ++++++++++++--
2 files changed, 18 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-p4import.txt b/Documentation/git-p4import.txt
index 714abbe..bf40b5a 100644
--- a/Documentation/git-p4import.txt
+++ b/Documentation/git-p4import.txt
@@ -10,6 +10,7 @@ SYNOPSIS
--------
[verse]
`git-p4import` [-q|-v] [--notags] [--authors <file>] [-t <timezone>]
+ [--start-with <change>]
<//p4repo/path> <branch>
`git-p4import` --stitch <//p4repo/path>
`git-p4import`
@@ -59,6 +60,11 @@ OPTIONS
etc. You only need to specify this once, it will be saved in
the git config file for the repository.
+\--start-with::
+ Start the import with the given Perforce change. A partial history can
+ be much faster to generate and is possible even with a low MaxScanRows
+ limit.
+
<//p4repo/path>::
The Perforce path that will be imported into the specified branch.
diff --git a/git-p4import.py b/git-p4import.py
index e7a52b3..c7a2033 100644
--- a/git-p4import.py
+++ b/git-p4import.py
@@ -33,7 +33,12 @@ def die(msg, *args):
sys.exit(1)
def usage():
- print "USAGE: git-p4import [-q|-v] [--authors=<file>] [-t <timezone>] [//p4repo/path <branch>]"
+ print "usage:"
+ print " git-p4import [-q|-v] [--notags] [--authors <file>] [-t <timezone>]"
+ print " [--start-with <change>]"
+ print " <//p4repo/path> <branch>"
+ print " git-p4import --stitch <//p4repo/path>"
+ print " git-p4import"
sys.exit(1)
verbosity = 1
@@ -41,6 +46,7 @@ logfile = file("/dev/null", "a")
ignore_warnings = False
stitch = 0
tagall = True
+start_with = 0
def report(level, msg, *args):
global verbosity
@@ -299,7 +305,8 @@ class git_command:
try:
opts, args = getopt.getopt(sys.argv[1:], "qhvt:",
- ["authors=","help","stitch=","timezone=","log=","ignore","notags"])
+ ["authors=","help","stitch=","timezone=","log=","ignore","notags",
+ "start-with="])
except getopt.GetoptError:
usage()
@@ -316,6 +323,8 @@ for o, a in opts:
usage()
if o in ("--ignore"):
ignore_warnings = True
+ if o in ("--start-with"):
+ start_with = int(a)
git = git_command()
branch=git.current_branch()
@@ -361,6 +370,7 @@ if stitch == 0:
top = git.top_change(branch)
else:
top = 0
+top = max(top, start_with)
changes = p4.changes(top)
count = len(changes)
if count == 0:
--
1.5.2
prev parent reply other threads:[~2007-06-03 3:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 16:47 git-p4import.py robustness changes Scott Lamb
2007-05-31 23:53 ` Junio C Hamano
2007-06-02 20:41 ` Scott Lamb
2007-06-02 21:33 ` Junio C Hamano
2007-06-02 23:21 ` Scott Lamb
2007-06-02 23:52 ` Junio C Hamano
2007-06-03 13:11 ` Simon Hausmann
2007-06-03 20:12 ` Scott Lamb
2007-06-04 5:54 ` Shawn O. Pearce
2007-06-04 6:09 ` Dana How
2007-06-04 6:18 ` Shawn O. Pearce
2007-06-04 7:19 ` Scott Lamb
2007-06-05 7:21 ` Simon Hausmann
2007-06-04 8:41 ` Marius Storm-Olsen
2007-06-04 5:56 ` Shawn O. Pearce
2007-06-12 21:46 ` Simon Hausmann
2007-06-13 21:06 ` Scott Lamb
2007-06-13 22:34 ` Simon Hausmann
2007-06-14 5:35 ` Shawn O. Pearce
2007-06-14 21:44 ` Simon Hausmann
2007-06-15 3:13 ` Shawn O. Pearce
2007-06-15 5:30 ` Marius Storm-Olsen, mstormo_git
2007-06-03 3:58 ` [PATCH 1/4] git-p4import: fix subcommand error handling Scott Lamb
2007-06-03 3:58 ` [PATCH 2/4] git-p4import: use lists of subcommand arguments Scott Lamb
2007-06-03 3:58 ` [PATCH 3/4] git-p4import: resume on correct p4 changeset Scott Lamb
2007-06-03 3:58 ` Scott Lamb [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11808431401213-git-send-email-slamb@slamb.org \
--to=slamb@slamb.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).