Michael Schoen wrote:
Can other folks replicate this behavior?
[devplp1] ~/rails-svn/autopilot $ svn log -q -r4191
------------------------------------------------------------------------
[devplp1] ~/rails-svn/autopilot $ svn log -q -r4192
------------------------------------------------------------------------
r4192 | rick | 2006-04-06 13:10:44 -0700 (Thu, 06 Apr 2006)
------------------------------------------------------------------------
The log messages for some revisions aren't coming through properly.
Michael Schoen wrote:
Odd behavior for changeset 4184 (breaking my automated testing script)
svn log -r4184 http://dev.rubyonrails.org/svn/rails/trunk
doesn't return madrobby's info.
Michael,
This is normal behavior.
Log won't show anything if there are no changes the location where log is
running. This is expected behavior, because if you're sitting in trunk and run
svn log, you don't want to see log messages for changes in any branches.
In this case, r4191 was David tagging 1.1.1 (which didn't get your Oracle fix,
it looks like) and it was a change in the tags directory.
svn log -v -r 4191 http://dev.rubyonrails.org/svn/rails
------------------------------------------------------------------------
r4191 | david | 2006-04-06 12:38:50 -0700 (Thu, 06 Apr 2006) | 1 line
Changed paths:
A /tags/rel_1-1-1 (from /trunk:4189)
Tagged 1.1.1
------------------------------------------------------------------------
If you want to see the log message for any revision, you need to use the root of
the Subversion repository. That's easy to get from a script if your client is
1.3.x:
svn info . | grep '^Repository Root:' | awk '{print $3}'
Parse for Ruby left as an exercise for thre reader.
Regards,
Blair
--
Blair Zajac
<[EMAIL PROTECTED]>
Subversion training, consulting and support
http://www.orcaware.com/svn/
_______________________________________________
Rails-core mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails-core
