blocks|key|1556873|text|为了与Jeff的建议保持一致，我自己回答这个问题，他建议使用Stackoverflow作为保存技术片段的地方……|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1556874|在命令行中使用：|1556875|p4+changes+-m1+@<clientname>|code-block|syntax|javascript|1556876|只需替换为您的客户规范的名称。这将产生表单的输出：|1556877|Change+12345+on+2008/08/21+by+joebloggs@mainline-client+'....top+line+of+description...'|1556878|其很容易被解析以提取变更列表编号。|1556879|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|R|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|T|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|U|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|V|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|P|$]]

Just to answer this myself in keeping with Jeff's suggestion of using Stackoverflow as a place to keep technical snippets....

From the command line use:

<pre><code>p4 changes -m1 @&lt;clientname&gt;
</code></pre>

And just replace with the name of your client spec. This will produce output of the form:

<pre><code>Change 12345 on 2008/08/21 by joebloggs@mainline-client '....top line of description...'
</code></pre>

Which is easily parsed to extract the changelist number.

blocks|key|1772116|text|您可以尝试在"p4+files“命令的输出中查找最大更改数。但是，工作目录不应该包含同步后提交。这只比|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1772117|p4+changes+-m1+"./...#have"|code-block|syntax|javascript|1772118|因为后者似乎在服务器上运行，并且可能由于"MaxResults“限制而在大型源码树上失败。|1772119|$+p4+changes+-m1+"./...#have"
Request+too+large+(over+850000);+see+'p4+help+maxresults'.

$+p4+-G+files+"./...#have"+%7C+python+c:/cygwin/usr/local/bin/p4lastchange.py
Files:+266948
2427657|1772120|其中p4lastchange.py基于2005年4月15日柯达信息网络/Ofoto的J.T.Goldstone的Using+P4G.py+From+the+Command+Line演示文稿中的代码。|offset|length|1772121|#!+/usr/bin/env+python
import+sys,+os,+marshal

if+os.name+==+"nt":
++++#+Disable+newline+translation+in+Windows.++Other+operating+systems+do+not
++++#+translate+file+contents.
++++import+msvcrt
++++msvcrt.setmode(+sys.stdin.fileno(),+os.O_BINARY+)

lastcl+=+0
num+=+0
try:
++++while+1:
++++++++dict+=+marshal.load(sys.stdin)
++++++++num+=+num+%2B+1
++++++++for+key+in+dict.keys():
++++++++++++#+print+"%25s:+%25s"+%25+(key,dict[key])
++++++++++++if+key+==+"change":
++++++++++++++++cl+=+int(dict[key])
++++++++++++++++if+cl+>+lastcl:
++++++++++++++++++++lastcl+=+cl
except+EOFError:
++++pass
print+"Files:+%25s"+%25+num
print+lastcl|1772122|entityMap|0|LINK|mutability|MUTABLE|url|http://www.perforce.com/perforce/conferences/us/2005/presentations/GoldstonePresentation.pdf^0|0|0|0|0|1K|Y|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|Z|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|10|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|11|8|@]|9|@]|A|$E|F]]|$1|K|3|L|5|6|7|12|8|@]|9|@$M|13|N|14|1|15]]|A|$]]|$1|O|3|P|5|D|7|16|8|@]|9|@]|A|$E|F]]|$1|Q|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|R|$S|$5|T|U|V|A|$W|X]]]]

You may try finding the maximum change number in the output of the "p4 files" command. The working directory should not contain post-sync commits, though. This is just a tad better than 

<pre><code>p4 changes -m1 "./...#have"
</code></pre>

as the latter seems to run on the server and may fail on big source trees due to "MaxResults" limits.

<pre><code>$ p4 changes -m1 "./...#have"
Request too large (over 850000); see 'p4 help maxresults'.

$ p4 -G files "./...#have" | python c:/cygwin/usr/local/bin/p4lastchange.py
Files: 266948
2427657
</code></pre>

where p4lastchange.py is based on the code from the <a href="http://www.perforce.com/perforce/conferences/us/2005/presentations/GoldstonePresentation.pdf" rel="noreferrer">Using P4G.py From the Command Line</a> presentation by J.T.Goldstone, Kodak Information Network/Ofoto, April 15, 2005.

<pre><code>#! /usr/bin/env python
import sys, os, marshal

if os.name == "nt":
 # Disable newline translation in Windows. Other operating systems do not
 # translate file contents.
 import msvcrt
 msvcrt.setmode( sys.stdin.fileno(), os.O_BINARY )

lastcl = 0
num = 0
try:
 while 1:
 dict = marshal.load(sys.stdin)
 num = num + 1
 for key in dict.keys():
 # print "%s: %s" % (key,dict[key])
 if key == "change":
 cl = int(dict[key])
 if cl &gt; lastcl:
 lastcl = cl
except EOFError:
 pass
print "Files: %s" % num
print lastcl
</code></pre>

blocks|key|1557002|text|到目前为止，我所发现的最好的方法就是同步到你想要构建的变更列表，然后使用-m1+//...#have+to+get+The+current+local+changelist+(revision)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1557003|p4+sync+@CHANGELIST_NUM+p4+-m1+//...#have+%7C+awk+'{print+$2}‘|1557004|为您提供您可以随时随地使用的更改列表编号。我目前正在寻找一种比更改-m1+//...#+p4更简单的方法。|1557005|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

The best I've found so far is to do your sync to whatever changelist you want to build and then use changes -m1 //...#have to get the current local changelist (revision).

p4 sync @CHANGELIST_NUM
p4 changes -m1 //...#have | awk '{print $2}'

Gives you the changelist number that you can the use wherever you want. I am currently looking for a simpler way than p4 changes -m1 //...#have.

blocks|key|1557053|text|您还可以使用cstat命令：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1557054|p4帮助cstat|1557055|cstat+--+Dump+change/sync+status+for+current+client

p4+cstat+[files...]

Lists+changes+that+are+needed,+had+or+partially+synced+in+the+current
client.+The+output+is+returned+in+tagged+format,+similar+to+the+fstat
command.

The+fields+that+cstat+displays+are:

++++change+++changelist+number
++++status+++'have',+'need'+or+'partial'|code-block|syntax|javascript|1557056|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|L|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|M|8|@]|9|@]|A|$G|H]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

You could also use the cstat command:

p4 help cstat

<pre><code>cstat -- Dump change/sync status for current client

p4 cstat [files...]

Lists changes that are needed, had or partially synced in the current
client. The output is returned in tagged format, similar to the fstat
command.

The fields that cstat displays are:

 change changelist number
 status 'have', 'need' or 'partial'
</code></pre>

blocks|key|1772349|text|整个仓库(不仅仅是您的工作区/客户端)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1772350|p4+counter+change|code-block|syntax|javascript|1772351|只需要告诉最后一个变更列表就行了。|1772352|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

For the whole depot (not just your workspace/client)

<pre><code>p4 counter change
</code></pre>

does the job, just telling the last changelist.

blocks|key|1772480|text|我不确定你是否得到了你想要的答案，但我也有类似的问题。我们的目标是在我们的记录器中写入项目的特定版本。问题是，当我们制作自己的makefile时，整个构建系统是由我们的配置管理控制的。这意味着所有那些说“同步到某件事然后做某件事”的解决方案并不能真正起作用，而且我不想在每次提交时手动更改版本(这肯定是错误的来源)。解决方案(实际上是在上面的一些答案中暗示的)是这样的:在我们的makefile中，I+do+p4+changes+-m1+"./...#have“result+is+Change+change_number+on+date+by+user@client+'msg‘我只是将消息创建成一个字符串，由记录器打印出来(更改编号是重要的元素，但对于快速确定某个版本是否包含您知道的更改，而无需强制检查)也很有用。希望这能有所帮助。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1772481|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I am not sure if you got the answer you needed but I had a similar problem. The goal was to write in our logger the specific version of the project. The problem was that while we are making our own makefile, the overall build system is controlled by our configuration management. This means that all the solutions which say "sync to something then do something" don't really work and I didn't want to manually change the version whenever we commit (a sure source for errors). 
The solution (which is actually hinted in some of the answers above) is this:
in our makefile, I do p4 changes -m1 "./...#have"
The result for this is Change change_number on date by user@client 'msg'
I simply create the message into a string which is printed by the logger (the change number is the important element but the other is also useful to quickly decide if a certain version contains changes you know you made yourself without going to perforce to check).
Hope this helps.

blocks|key|1772535|text|对于我的客户来说，“推荐”使用p4+changes+-m1+@clientname大约需要10分钟。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1772536|这是我使用的：|1772537|p4+cstat+...#have+%7C+grep+change+%7C+awk+'$3+>+x+{+x+=+$3+};END+{+print+x+}'|code-block|syntax|javascript|1772538|对于同一个客户端，需要2.1秒|1772539|entityMap^0|F|Q|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Q|8|@$9|R|A|S|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|T|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|U|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|V|8|@]|D|@]|E|$]]|$1|O|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|P|$]]

<code>p4 changes -m1 @clientname</code> which is the "recommended" way to do it for my client takes about 10 minutes

this is what I use:

<pre><code>p4 cstat ...#have | grep change | awk '$3 &gt; x { x = $3 };END { print x }'
</code></pre>

for the same client takes 2.1 seconds

A question that occasionally arises is what is the best way to determine the changelist that you last synced to in Perforce. This is often needed for things like injecting the changelist number into the revision info by the automatic build system.

Determining the last changelist synced to in Perforce

服务器

Windows

偶尔会出现的一个问题是，确定上次在Perforce中同步到的更改列表的最佳方式是什么。对于自动构建系统将变更列表编号注入修订信息之类的事情，通常需要这样做。

问正在确定在Perforce中同步到的最后一个更改列表
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问正在确定在Perforce中同步到的最后一个更改列表EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问正在确定在Perforce中同步到的最后一个更改列表
EN