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

Re: Git p4 sync changelist interval

From
Luke Diamand <luke@diamand.org>
Date
Jun 4, 2017, 11:09 UTC
Message-ID
<CAE5ih7-Nmy2J6zO9mx7g=L7Ey9PnVUcD3wnXBN4_0znwOHaUeQ@mail.gmail.com>
In-Reply-To
<CAPRL90JeQ3i1m7ydYzTCFgtZ4cC+gYEXFeAKvCuAVwPLXpsgXg@mail.gmail.com>
On 4 June 2017 at 10:56, Андрей Ефанов <1134togo@gmail.com> wrote:
Show 11 quoted lines
> Hello,
>
> My goal is to sync the repository from p4 using an interval of
> changelists so that the first changelist version of the repository
> would be considered as an initial commit.
> So I used the following command:
>
>  git p4 clone //depot@cl1,cl2
>
> And when it finished, the files, that were created before the cl1 were
> not in the HEAD.

Do you mean that if foo.c was created at cl1+1, that after doing the clone, it wasn't there?

If so, that doesn't sound right to me.
I have just tried doing what I think you mean:
1. Create p4 depot
2. Add foo.c (at CL 2)
3. Add bar.c (at CL 3)
4. git-p4 clone //depot@2,3
I end up with both files.
Show 5 quoted lines
>
> The problem, as I see it, is that before syncing changes in the given
> range, p4 task does not sync to cl1 version of the repo, and applies
> commits to the empty repository.
> Is it a bug or my misunderstanding of how git p4 should work?

Possibly I'm misunderstanding what you're doing! Can you give a sequence of steps to show the problem?

Thanks! Luke

Previous: Андрей ЕфановNext: Андрей Ефанов
Message 2 of 8 in “Git p4 sync changelist interval”
  1. Андрей ЕфановJun 4, 2017
  2. Luke DiamandJun 4, 2017
  3. Fwd: Git p4 sync changelist intervalАндрей Ефанов, Jun 5, 2017
  4. Luke DiamandJun 5, 2017
  5. Luke DiamandJun 6, 2017
  6. Luke DiamandJun 6, 2017
  7. Андрей ЕфановJun 6, 2017
  8. Luke DiamandJun 6, 2017

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.