{"id":2707,"date":"2012-03-12T21:19:53","date_gmt":"2012-03-12T13:19:53","guid":{"rendered":"http:\/\/jpuyy.com\/?p=2707"},"modified":"2023-05-07T00:58:22","modified_gmt":"2023-05-06T16:58:22","slug":"svn-log-can-not-see-just-committed","status":"publish","type":"post","link":"https:\/\/jpuyy.com\/?p=2707","title":{"rendered":"svn log \u4e0d\u4f1a\u663e\u793a\u521a\u521a\u63d0\u4ea4\u7684\u5185\u5bb9"},"content":{"rendered":"<blockquote><p>&nbsp;<\/p>\n<p>If you make a commit and immediately type svn log with no arguments, you may notice that your most recent commit doesn&#8217;t show up in the list of log messages. This is due to a combination of the behavior of svn commit and the default behavior of svn log. First, when you commit changes to the repository, svn bumps only the revision of files (and directories) that it commits, so usually the parent directory remains at the older revision (See \u7b2c 3.5.1 \u8282 \u201c\u66f4\u65b0\u548c\u63d0\u4ea4\u662f\u5206\u5f00\u7684\u201d for an explanation of why). svn log then defaults to fetching the history of the directory at its current revision, and thus you don&#8217;t see the newly committed changes. The solution here is to either update your working copy or explicitly provide a revision number to svn log by using the &#8211;revision (-r) option.<\/p><\/blockquote>\n<p>\u5982\u679c\u521a\u521a\u63d0\u4ea4\u5c31\u7528svn log\u547d\u4ee4\uff0c\u5219\u4e0d\u4f1a\u663e\u793a\u521a\u521a\u63d0\u4ea4\u7684\u5185\u5bb9\u3002\u56e0\u4e3asvn commit\u64cd\u4f5c\u4e0esvn log\u64cd\u4f5c\u4e4b\u95f4\u7684\u8054\u7cfb\uff0c\u5f53\u63d0\u4ea4\u7684\u65f6\u5019\uff0c\u53ea\u4f1a\u6539\u53d8\u5f53\u524d\u6587\u4ef6\u6216\u76ee\u5f55\u7684\u7248\u672c\u53f7\uff0csvn log\u4f1a\u6293\u53d6\u5f53\u524d\u7248\u672c\uff0c\u800c\u4e0d\u4f1a\u7ba1\u65b0\u63d0\u4ea4\u7684\u3002\u53ef\u4ee5\u5148svn update \u518d\u67e5\u770b\u6216\u7528\u7c7b\u4f3csvn log -r 8 -v\u6765\u67e5\u770b\u3002<\/p>\n","protected":false},"excerpt":{"rendered":"<p>&nbsp; If you make a commit and immediately type svn log with no arguments, you may notice that your most recent commit doesn&#8217;t show up in the list of log messages. This is due to a combination of the behavior of svn commit and the default behavior of svn log. First, when you commit changes [&hellip;]<\/p>\n","protected":false},"author":3,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[23],"class_list":["post-2707","post","type-post","status-publish","format-standard","hentry","category-linux","tag-summary"],"_links":{"self":[{"href":"https:\/\/jpuyy.com\/index.php?rest_route=\/wp\/v2\/posts\/2707","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jpuyy.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jpuyy.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jpuyy.com\/index.php?rest_route=\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/jpuyy.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2707"}],"version-history":[{"count":4,"href":"https:\/\/jpuyy.com\/index.php?rest_route=\/wp\/v2\/posts\/2707\/revisions"}],"predecessor-version":[{"id":2710,"href":"https:\/\/jpuyy.com\/index.php?rest_route=\/wp\/v2\/posts\/2707\/revisions\/2710"}],"wp:attachment":[{"href":"https:\/\/jpuyy.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2707"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jpuyy.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2707"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jpuyy.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2707"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}