Olivier Dehon wrote: > On Sat, 2010-02-27 at 08:43 -0600, Ryan Schmidt wrote: >> On Feb 27, 2010, at 08:36, Olivier Dehon wrote: >>> On Fri, 2010-02-26 at 22:15 -0800, Alexey Neyman wrote: >>>> It seems that I encountered a bug in 'svnlook pl --revprop': it fails with >>>> the following message: >>>> >>>> $ svnlook pl --revprop -t 10547-86b /svn/test-svn >>>> svnlook: Invalid revision number '-1' >>> Looks like you need to use "svnlook info -t" to access the values of the >>> properties that are going to be set on the revision-to-be (svn:log, >>> svn:author, ...) >> Why can't he use "svnlook pl --revprop -t" as he suggested? "svnlook help >> pl" suggests this should work. >> > > Agreed, it might be a missing feature. I was just trying to suggest a > workaround for what the OP wanted to achieve.
This is not an oversight. Subversion's public interfaces have always split trees of changes in the repository into two non-overlapping segments: revisions ("which are sets of tree changes that have been promoted into new, numbered, revisions by the commit process"), and transactions ("which are sets of tree changes not yet promoted into revisions"). We believe that the fact that those "revisions" are just promoted "transactions" (meaning, that you can still address them by their transaction name) is a bit of an implementation detail that needn't be revealed through the public interfaces to Subversion. -- C. Michael Pilato <cmpil...@collab.net> CollabNet <> www.collab.net <> Distributed Development On Demand
signature.asc
Description: OpenPGP digital signature