From: "Laurent Charrière" <lcharriere@promptu.com>
To: git@vger.kernel.org
Subject: git-p4 and initial import
Date: Thu, 10 Jul 2014 15:45:16 +0200 [thread overview]
Message-ID: <53BE98EC.9000200@promptu.com> (raw)
I've used git-p4 for several years now and it's generally working well
for me.
The only thing that bugs me at this time is having to re-clone
regularly. Here is how this happens:
* Say my p4 client maps //foo/bar/... to /home/jdoe/perforce/foo/bar/...
(I don't want to clone the entire repo, because it's too big).
* I do git p4 clone --use-client-spec //foo /home/jdoe/git/foo, work
with it, all goes well.
* Meanwhile, at some point somebody else adds //foo/baz.
* Eventually I need //foo/baz. I add it to my p4 client.
* Naturally, git-p4 won't pick up the changes, because they happened
before I added //foo/baz to my client.
* So I git reset --hard to the first commit, delete even that using git
update-ref -d HEAD, then again I do git p4 clone //foo
/home/jdoe/git/foo. When the repo gets big, this takes a lot of time.
So, I have a few questions:
1. Am I doing this wrong? Is there another way I could proceed?
2. It occurred to me that when I re-clone a repository using
--use-client-spec, I already have everything I need in my local copy of
the p4 client. Why does git-p4 need to redownload everything from the
repository? Could we find a way to tell it to p4 sync, then fetch the
files from the local copy? Or is there a way I can copy everything over
from my local client and pretend this is the initial import?
next reply other threads:[~2014-07-11 6:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-10 13:45 Laurent Charrière [this message]
2014-07-12 17:56 ` git-p4 and initial import Pete Wyckoff
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=53BE98EC.9000200@promptu.com \
--to=lcharriere@promptu.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).