git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git p4 clone - HEAD + partial history

From
FusionX86 <fusionx86@gmail.com>
Date
May 12, 2015, 20:23 UTC
Message-ID
<CAFcBi89+FuvB=VF3nCDy7_xrwz=Of_omkCn35MdXBwhy6VckjQ@mail.gmail.com>
In-Reply-To
<55525A99.9070702@diamand.org>
Thanks Luke! I'll give that a shot.
On Tue, May 12, 2015 at 1:55 PM, Luke Diamand <luke@diamand.org> wrote:
Show 34 quoted lines
> On 12/05/15 20:31, FusionX86 wrote:
>>
>> Hello,
>>
>> I'm migrating my company from Perforce to Git. There is history in
>> Perforce that goes back to 2006 and I'd like to migrate it with some,
>> but not all of the history. I'm not having luck so far.
>>
>>  From what I see, a simple git p4 clone grabs HEAD only. Using @all
>> grabs all history and is way too much to migrate. I have tried using
>> //depot/folder@2015/01/01,@all when cloning, but it doesn't grab the
>> current stuff in HEAD.
>>
>> Is it possible to grab what is currently in HEAD and the last few
>> months of history only?
>
>
> What I've done in the past is just find a commit that's about the right
> date, and clone from there.
>
> i.e.
>
> $ git p4 clone //depot/folder/...@12345
> $ git p4 sync
>
> The usual problem I have after that is that P4 repos can get very large, and
> the process can quite time consuming....
>
>> --
>> To unsubscribe from this list: send the line "unsubscribe git" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>>
>
Previous: Luke Diamand
Message 3 of 3 in “git p4 clone - HEAD + partial history”
  1. FusionX86May 12, 2015
  2. Luke DiamandMay 12, 2015
  3. FusionX86May 12, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.