From: "Benjamin Sergeant" <bsergean@gmail.com>
To: git@vger.kernel.org
Subject: Re: p4 + svn + git
Date: Thu, 7 Jun 2007 22:27:30 -0700 [thread overview]
Message-ID: <1621f9fa0706072227s7b64e4abq682b53eb920c8f53@mail.gmail.com> (raw)
In-Reply-To: <1621f9fa0706072145s3ea6d5cdt3c3e6a2eaaffa14c@mail.gmail.com>
On 6/7/07, Benjamin Sergeant <bsergean@gmail.com> wrote:
> That might be too much, but let's ask anyway...
This is probably too much, so on to the next question:
Is there a perforce equivalent of git-svn ?
What I'd like to do:
My main Linux machine will be the gateway.
1. I 'clone' the perforce tree with git-p4. I now have a .git, a full repo.
Can I use this as the equivalent of a subversion server, so that every
other machines pull / push from it.
And once in a while (weekly basis), I push the work that's been done
in git to perforce using the Linux box.
Doest that make sense ?
Thanks,
Benjamin.
>
> My company uses perforce.
> I took a snapshot of some code checked out from perforce (a single
> branch), that I imported into subversion, a while ago, and started
> working with svn only. I have different Unix machines checking in /
> out code code from the subversion server (with svn), and I'd like to
> keep it this way (if possible).
>
> I'm wondering if I could use git as a gateway between both systems, to
> merge code in both direction (svn <-> perforce).
>
> Is this possible, with the help of git-p4import, git-svn, and using
> several branches ?
>
> Thanks,
> Benjamin.
>
next prev parent reply other threads:[~2007-06-08 5:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 4:45 p4 + svn + git Benjamin Sergeant
2007-06-08 5:27 ` Benjamin Sergeant [this message]
2007-06-08 5:31 ` Benjamin Sergeant
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=1621f9fa0706072227s7b64e4abq682b53eb920c8f53@mail.gmail.com \
--to=bsergean@gmail.com \
--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).