Sorry, forgot to reply-to-all, here is my response again:
On Tue, Oct 30, 2012 at 11:44 AM, Arthur <a.fou...@amesys.fr> wrote:
> The problem :
> Importing revision 7727 (100%)Traceback (most recent call last):
> File "/usr/bin/git-p4", line 3183, in <module>
> File "/usr/bin/git-p4", line 3177, in main
> if not cmd.run(args):
> File "/usr/bin/git-p4", line 3048, in run
> if not P4Sync.run(self, depotPaths):
> File "/usr/bin/git-p4", line 2911, in run
> File "/usr/bin/git-p4", line 2618, in importChanges
> File "/usr/bin/git-p4", line 2198, in commit
> epoch = details["time"]
> KeyError: 'time'
Are you permanently converting a project, or are you planning to
continue submitting to perforce with git-p4?
I have seen similar bugs myself when using the --detect-branches
option. The branch detection in git-p4 is flaky anyway: it is limited
what it can handle, and it used to require correct perforce branch
specs at least, so I would recommend not using it unless you know what
it is doing under the hood.
Instead I would just clone a single branch at a time (drop the
--detect-branches) and work on that.
I do this even in the rare cases when I need more than one perforce
branch in the same git repo - there are other ways to achieve the same
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html