将 P4 移动操作放入非默认更改列表中

发布于 2024-09-26 18:11:19 字数 242 浏览 3 评论 0原文

我正在尝试执行 p4 move 来保留 perforce 历史记录。 P4 移动在我的默认更改列表中创建了删除/添加操作。该文档向我保证,p4 move 将通过“集成记录”保留历史记录。

现在我想提交更改列表的 p4 move(删除/添加)操作部分。我如何确保 Perforce 将正确执行移动,而不是按照我的更改列表当前指示删除/添加并丢失历史记录?我可以查看提交变更列表时是否会创建“激活记录”吗?

I'm trying to do a p4 move to retain the perforce history. P4 moves created a delete/add operation in my default changelist. The documentation assures me that p4 move will retain history via an 'integration record'.

Now I want to submit the p4 move (delete/add) operation part of a changelist. How do I make sure that Perforce will do the move properly rather then delete/add as currently indicated by my changelist and lose the history? Can I see if the 'activation record' will created when the changelist is submitted?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。

评论(3

〗斷ホ乔殘χμё〖 2024-10-03 18:11:19

您可以使用p4打开来查看更改列表中打开的文件的状态。以下命令序列说明了 p4 move 期间发生的情况。

$ p4 open icons.zip
$ p4 opened 
//full/depot/path/to/icons.zip#1 - edit default change (ubinary)
$ p4 move icons.zip foo.zip
//full/depot/path/to/foo.zip#1 - moved from //full/depot/path/to/icons.zip#1
$ p4 opened
//full/depot/path/to/foo.zip#1 - move/add default change (ubinary)
//full/depot/path/to/icons.zip#1 - move/delete default change (ubinary)
$ p4 changelist 
Change 350425 created with 2 open file(s).
$ p4 opened
//full/depot/path/to/foo.zip#1 - move/add change 350425 (ubinary)
//full/depot/path/to/icons.zip#1 - move/delete change 350425 (ubinary)

正如您所看到的,创建新的挂起更改列表根本不会更改打开文件的状态,它与 move/add + move/delete 操作相关。如果这不是您要查找的内容,请编辑您的问题。

注意:以上内容是使用 P4D/2009.2(服务器)和 p4/2010.1(客户端)进行测试的。

You can use p4 opened to see the status of the opened files in your changelist. The following sequence of commands illustrates what happens during a p4 move.

$ p4 open icons.zip
$ p4 opened 
//full/depot/path/to/icons.zip#1 - edit default change (ubinary)
$ p4 move icons.zip foo.zip
//full/depot/path/to/foo.zip#1 - moved from //full/depot/path/to/icons.zip#1
$ p4 opened
//full/depot/path/to/foo.zip#1 - move/add default change (ubinary)
//full/depot/path/to/icons.zip#1 - move/delete default change (ubinary)
$ p4 changelist 
Change 350425 created with 2 open file(s).
$ p4 opened
//full/depot/path/to/foo.zip#1 - move/add change 350425 (ubinary)
//full/depot/path/to/icons.zip#1 - move/delete change 350425 (ubinary)

As you can see, the creation of a new pending changelist didn't change the status of the opened files at all, it pertains the move/add + move/delete action. If this is not what you were looking for, please edit your question.

Note: the above was tested with P4D/2009.2 (Server) and p4/2010.1 (Client).

不离久伴 2024-10-03 18:11:19

我不知道如何查询待处理的移动操作。

如果我不知道什么操作正在等待,但我知道它应该是一个移动,并且提交记录是一个移动对我来说至关重要,那么我将恢复有问题的文件并再次调用 p4 move< /代码> 他们。

更新:我在 另一个答案 p4 打开 报告待处理的移动。

I have no idea how to query for a pending move operation.

If I don't know what operation is pending but I know that it should be a move and it is vital for me that the submit record be a move, then I would revert the files in question and again call p4 move on them.

Update: I see in the other answer that p4 opened reports pending moves.

初心 2024-10-03 18:11:19

P4 为移动创建 2 个更改:

移动/添加和移动/删除

您可以提交这些更改,并且两者都将出现在更改列表中。

P4 creates 2 changes for move:

move/add and move/delete

You can commit those and both will be in the changelist.

~没有更多了~
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文