git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Patrick Rouleau <prouleau72@gmail.com>
To: Lars Schneider <larsxschneider@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-p4: cloning with a change number does not import all files
Date: Sat, 2 Dec 2017 10:35:23 -0500	[thread overview]
Message-ID: <CAL1_K8A=7xmLCYzWa0ejtwjy9P+rD+D0cqz+kOXCaQWOgQfuEw@mail.gmail.com> (raw)
In-Reply-To: <A6F43B7B-F0AF-46E7-B34B-7D54493E2C8B@gmail.com>

On Fri, Dec 1, 2017 at 7:45 AM, Lars Schneider <larsxschneider@gmail.com> wrote:
> 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:
> https://www.youtube.com/watch?v=QNixDNtwYJ0
>
> Cheers,
> Lars

Sadly, there is no way I convince the company to switch to git. They
have acquired
many companies in the past years and they have standardized around Perforce.
It is in part because they want access control and they need to store
a lot of binary
files (including big VM images).

I keep this video close to explain why I like git:
https://www.youtube.com/watch?v=o4PFDKIc2fs

Regards,
P. Rouleau

  reply	other threads:[~2017-12-02 15:35 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
2017-12-02 15:35       ` Patrick Rouleau [this message]
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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to='CAL1_K8A=7xmLCYzWa0ejtwjy9P+rD+D0cqz+kOXCaQWOgQfuEw@mail.gmail.com' \
    --to=prouleau72@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=larsxschneider@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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).