From: Ian Wienand <ianw@vmware.com>
To: Endre Czirbesz <endre@czirbesz.hu>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git to p4 conversion
Date: Thu, 03 Feb 2011 10:23:26 -0800 [thread overview]
Message-ID: <4D4AF29E.7070509@vmware.com> (raw)
In-Reply-To: <AANLkTi=0TSD6p7WtsVzx=pq8=GVu+jHUdxt1bnC++CT+@mail.gmail.com>
On 03/02/11 05:52, Endre Czirbesz wrote:
> I have some small (and flat) git repos, which I would like to migrate
> into a perforce depot keeping their histories. I tried git-p4 without
> any success, and I did not find a good manual for it.
What exactly did you try?
Theoretically, you could clone your new, empty, company-mandated p4
tree into a fresh git repo, get your existing code onto a new branch
in this fresh repo (it's already in git, right, so that should be
easy), then use 'git-p4 submit' to submit that branch back to p4.
> Is there any step-by-step tutorial out there? Is there any living human
> who ever made a successful conversion in this direction?
I'm not aware of an existing tutorial for this, sorry
-i
next prev parent reply other threads:[~2011-02-03 18:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-03 13:52 git to p4 conversion Endre Czirbesz
2011-02-03 18:23 ` Ian Wienand [this message]
2011-02-03 19:50 ` Endre Czirbesz
2011-02-04 0:03 ` Vitor Antunes
2011-02-04 9:25 ` Tor Arvid Lund
2011-02-04 10:49 ` Endre Czirbesz
2011-02-04 14:01 ` Tor Arvid Lund
2011-02-04 16:08 ` Endre Czirbesz
[not found] ` <AANLkTimGaPQ=hRp+2pvw-hAOg+wp50nvc_sv9jNTay=n@mail.gmail.com>
2011-02-04 16:52 ` Endre Czirbesz
2011-02-05 0:53 ` Tor Arvid Lund
2011-02-05 1:11 ` Vitor Antunes
2011-02-07 13:57 ` Endre Czirbesz
2011-02-07 14:13 ` Tor Arvid Lund
2011-02-07 15:07 ` Endre Czirbesz
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=4D4AF29E.7070509@vmware.com \
--to=ianw@vmware.com \
--cc=endre@czirbesz.hu \
--cc=git@vger.kernel.org \
/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).