From: Dmitry Smirnov <divis1969@gmail.com>
To: git@vger.kernel.org
Subject: Re: Git drawbacks?
Date: Wed, 11 Nov 2009 10:21:18 +0000 (UTC) [thread overview]
Message-ID: <loom.20091111T105932-300@post.gmane.org> (raw)
In-Reply-To: loom.20091106T160709-387@post.gmane.org
Dmitry Smirnov <divis1969 <at> gmail.com> writes:
Ok, I have heard a lot of perfect words about Git. I'm almost on your side :-)
Just need some advice on (small for Git, I hope) problem.
I'm trying to import P4 depot into Git (for mirroring purpose).
It seems a non-trivial task with the current git-p4 script.
Perhaps, I had selected a wrong way: i'm trying to import some client.
In fact, as I said in previous mails, typically I have few similar clients.
So, maybe it is simpler to import some set of branches (which I suppose a little
bit simpler with git-p4).
Unfortunaley, the directory structure of the depot differs from client's (i.e.
working tree differs from repository tree).
For example,
//depot/component/version could be mapped to the
<root_of_working_tree>/component.
Thus if I import //depot/component/version1 and //depot/component/version2
as is, I should be able to checkout either version1 or version2.
Note that there could be few components in the same working tree:
//depot/component1/version1 (mapped to <root>/component1)
//depot/component2/versionX (mapped to <root>/component2)
//depot/component3/versionY (mapped to <root>/component3)
With Perforce, there could also be a more complex mappings, but maybe we will
discuss it later).
Is there any way to make this mapping with Git? Should I invent some kind of
tool like 'repo' or there is a simpler way?
Dmitry
prev parent reply other threads:[~2009-11-11 10:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 16:17 Git drawbacks? Dmitry Smirnov
2009-11-06 16:49 ` Avery Pennarun
2009-11-06 17:35 ` Dmitry Smirnov
2009-11-06 17:41 ` Jacob Helwig
2009-11-06 17:51 ` Avery Pennarun
2009-11-06 18:57 ` david
2009-11-09 7:53 ` Dmitry Smirnov
2009-11-09 14:34 ` Jacob Helwig
2009-11-09 15:59 ` Dmitry Smirnov
2009-11-09 16:21 ` Jacob Helwig
2009-11-09 15:48 ` Dmitry Potapov
2009-11-09 16:11 ` Dmitry Smirnov
2009-11-09 18:34 ` Dmitry Potapov
2009-11-10 8:31 ` Dmitry Smirnov
2009-11-10 13:45 ` Dmitry Potapov
2009-11-10 14:14 ` Dmitry Smirnov
2009-11-10 16:15 ` Paolo Bonzini
2009-11-09 18:47 ` B Smith-Mannschott
2009-11-09 21:06 ` Dmitry Potapov
2009-11-10 8:51 ` Dmitry Smirnov
2009-11-10 14:04 ` Dmitry Potapov
2009-11-10 14:54 ` Dmitry Smirnov
2009-11-10 16:20 ` Paolo Bonzini
2009-11-10 23:43 ` Dmitry Potapov
2009-11-10 9:08 ` Dmitry Smirnov
2009-11-09 7:22 ` Dmitry Smirnov
2009-11-11 10:21 ` Dmitry Smirnov [this message]
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=loom.20091111T105932-300@post.gmane.org \
--to=divis1969@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.