From: "Govind Salinas" <govindsalinas@gmail.com>
To: git@vger.kernel.org
Subject: git-p4 question
Date: Thu, 9 Aug 2007 21:53:37 -0500 [thread overview]
Message-ID: <69b0c0350708091953wdc9c22vd2b17b1edd1c5cd2@mail.gmail.com> (raw)
Hi All,
Me again with more dumb git-perforce questions.
I have been toying with git-p4 and I think it does everything I want
except the crazy client map support. I figure I don't really need
this. My client is something like this:
//depot/sane/... //clientroot/crazy/...
//depot/stuff/... //clientroot/dumb/...
//depot/otherstuff/... //clientroot/dumb/...
//depot/my/product/... //clientroot/src/realworkhere/...
My "working directory" looks something like this:
c:\path\crazy\xyz_from_perforce
c:\path\crazy\abc_from_huge_binary_fileshare_notinp4
c:\path\dumb\...
c:\path\src\realworkhere\...
If I can just sync from p4 and then sync my binary share and THEN tell
git-p4 that //depot/my/product/... maps to c:\path\src\realworkhere,
get it to import history etc, then I would be set.
Is this at all possible to do with git-p4?
If not, what sort of work would be necessary to add that (considering
that I am a git noob).
Thanks for the help.
-Govind
next reply other threads:[~2007-08-10 2:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 2:53 Govind Salinas [this message]
2007-08-10 8:06 ` git-p4 question Alex Riesen
2007-08-10 8:10 ` Alex Riesen
2007-08-10 15:17 ` Govind Salinas
2007-08-10 16:25 ` Alex Riesen
-- strict thread matches above, loose matches on Subject: below --
2015-04-20 16:29 git-p4 Question Fusion Xavier
2015-04-20 16:41 FusionX86
2015-04-20 18:23 ` Sam Vilain
2015-04-21 13:23 ` FusionX86
2015-04-20 19:26 ` Luke Diamand
2015-04-21 13:33 ` FusionX86
2015-04-21 16:53 ` Luke Diamand
2015-04-23 13:42 ` FusionX86
2015-04-24 9:20 ` Luke Diamand
2015-04-24 14:36 ` FusionX86
2015-04-26 22:27 ` Luke Diamand
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=69b0c0350708091953wdc9c22vd2b17b1edd1c5cd2@mail.gmail.com \
--to=govindsalinas@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).