From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Govind Salinas" <govindsalinas@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-p4 question
Date: Fri, 10 Aug 2007 10:06:15 +0200 [thread overview]
Message-ID: <81b0412b0708100106m3123a504p16309b6e06cd9609@mail.gmail.com> (raw)
In-Reply-To: <69b0c0350708091953wdc9c22vd2b17b1edd1c5cd2@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 637 bytes --]
On 8/10/07, Govind Salinas <govindsalinas@gmail.com> wrote:
> 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.
git-p4-import.bat can import a state from the client have-list,
but it does not import the history. It can import the history
separately, so that you can stitch it into a merge which will be
the state imported from the client. Complicated, but I couldn't
bring myself to figure out the history automatically.
The script attached (sorry for .gz, gmail wont let me send a .bat).
[-- Attachment #2: git-p4-import.gz --]
[-- Type: application/x-gzip, Size: 15646 bytes --]
next prev parent reply other threads:[~2007-08-10 8:07 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 2:53 git-p4 question Govind Salinas
2007-08-10 8:06 ` Alex Riesen [this message]
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=81b0412b0708100106m3123a504p16309b6e06cd9609@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=govindsalinas@gmail.com \
/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).