git p4: gracefully fail if some commits could not be applied

If a commit fails to apply cleanly to the p4 tree, an interactive
prompt asks what to do next.  In all cases (skip, apply, write),
the behavior after the prompt had a few problems.

Change it so that it does not claim erroneously that all commits
were applied.  Instead list the set of the patches under
consideration, and mark with an asterisk those that were
applied successfully.  Like this example:

    Applying 592f1f9 line5 in file1 will conflict
    ...
    Unfortunately applying the change failed!
    What do you want to do?
    [s]kip this patch / [a]pply the patch forcibly and with .rej files / [w]rite the patch to a file (patch.txt) s
    Skipping! Good luck with the next patches...
    //depot/file1#4 - was edit, reverted
    Applying b8db1c6 okay_commit_after_skip
    ...
    Change 6 submitted.
    Applied only the commits marked with '*':
      592f1f9 line5 in file1 will conflict
    * b8db1c6 okay_commit_after_skip

Do not try to sync and rebase unless all patches were applied.
If there was a conflict during the submit, there is sure to be one
at the rebase.  Let the user to do the sync and rebase manually.

This changes how a couple tets in t9810-git-p4-rcs.sh behave:

    - git p4 now does not leave files open and edited in the
      client

    - If a git commit contains a change to a file that was
      deleted in p4, the test used to check that the sync/rebase
      loop happened after the failure to apply the change.  Since
      now sync/rebase does not happen after failure, do not test
      this.  Normal rebase machinery, outside of git p4, will let
      rebase --skip work.

Signed-off-by: Pete Wyckoff <pw@padd.com>
Acked-by: Luke Diamand <luke@diamand.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
Pete Wyckoff
2012-09-09 16:16:03 -04:00
committed by Junio C Hamano
parent 8c29135086
commit 67b0fe2eb6
3 changed files with 128 additions and 56 deletions

View File

@ -1088,7 +1088,10 @@ class P4Submit(Command, P4UserMap):
return False
def applyCommit(self, id):
print "Applying %s" % (read_pipe("git log --max-count=1 --pretty=oneline %s" % id))
"""Apply one commit, return True if it succeeded."""
print "Applying", read_pipe(["git", "show", "-s",
"--format=format:%h %s", id])
(p4User, gitEmail) = self.p4UserForCommit(id)
@ -1206,7 +1209,7 @@ class P4Submit(Command, P4UserMap):
p4_revert(f)
for f in filesToAdd:
os.remove(f)
return
return False
elif response == "a":
os.system(applyPatchCmd)
if len(filesToAdd) > 0:
@ -1312,6 +1315,7 @@ class P4Submit(Command, P4UserMap):
os.remove(f)
os.remove(fileName)
return True # success
# Export git tags as p4 labels. Create a p4 label and then tag
# with that.
@ -1487,14 +1491,16 @@ class P4Submit(Command, P4UserMap):
if gitConfig("git-p4.detectCopiesHarder", "--bool") == "true":
self.diffOpts += " --find-copies-harder"
while len(commits) > 0:
commit = commits[0]
commits = commits[1:]
self.applyCommit(commit)
applied = []
for commit in commits:
ok = self.applyCommit(commit)
if ok:
applied.append(commit)
if len(commits) == 0:
print "All changes applied!"
chdir(self.oldWorkingDirectory)
chdir(self.oldWorkingDirectory)
if len(commits) == len(applied):
print "All commits applied!"
sync = P4Sync()
sync.run([])
@ -1502,6 +1508,20 @@ class P4Submit(Command, P4UserMap):
rebase = P4Rebase()
rebase.rebase()
else:
if len(applied) == 0:
print "No commits applied."
else:
print "Applied only the commits marked with '*':"
for c in commits:
if c in applied:
star = "*"
else:
star = " "
print star, read_pipe(["git", "show", "-s",
"--format=format:%h %s", c])
print "You will have to do 'git p4 sync' and rebase."
if gitConfig("git-p4.exportLabels", "--bool") == "true":
self.exportLabels = True
@ -1512,6 +1532,10 @@ class P4Submit(Command, P4UserMap):
missingGitTags = gitTags - p4Labels
self.exportGitTags(missingGitTags)
# exit with error unless everything applied perfecly
if len(commits) != len(applied):
sys.exit(1)
return True
class View(object):