mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Lars Schneider <>
To: Patrick Rouleau <>
Subject: Re: git-p4: cloning with a change number does not import all files
Date: Fri, 1 Dec 2017 13:45:52 +0100	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

> On 29 Nov 2017, at 04:48, Patrick Rouleau <> wrote:
> Hi,
> On Mon, Nov 27, 2017 at 7:52 AM, Lars Schneider
> <> wrote:
>> what is your goal here? Do you want to convert the repo to Git or do you
>> want to use Git to interact with a P4 repo?
> I want to use git to interact with a P4 repo. I am used to git tools
> and I prefer them to
> P4V. Visual Studio is also slower with P4 plugin and I hate P4
> approach to check out
> a file before modifying it. The .sln files always get check outed for no reason.
> I am working remotely. The P4 server is behind a VPN. That one reason
> I am trying to
> clone from some point in the past. I also want to have some history to
> see from where
> come the code and from who.

Oh, I am with you. However, I only used git-p4 for a very short time in the 
way you want to use it. Therefore, I don't have much experience in that kind 
of usage pattern. I was able to convice my management to move all source to 
Git and I used git-p4 to migrate the repositories ;-)

Here is a talk on the topic if you want to learn more:


  reply	other threads:[~2017-12-01 12:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-25 20:35 git-p4: cloning with a change number does not import all files Patrick Rouleau
2017-11-27 12:52 ` Lars Schneider
2017-11-29  3:48   ` Patrick Rouleau
2017-12-01 12:45     ` Lars Schneider [this message]
2017-12-02 15:35       ` Patrick Rouleau
2017-12-02 17:55         ` Luke Diamand
2017-12-02 19:58           ` Patrick Rouleau

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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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.
Code repositories for project(s) associated with this public inbox

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 read-only IMAP folder(s) and NNTP newsgroup(s).