On Wed, 20 Dec 2006, Ramanathan Muthaiah wrote:
> >> >Hello, guys. I noticed that when svnlook could not find a property on a
> >> >path in a transaction it printed revision -1, although I expected it
> >> >would print the transaction name I had passed to it.
> >> >
> >> >G:\tmp>svnlook pget rep somename tempDir/myTemp.txt -t 16-1
> >> >svnlook: Property 'somename' not found on path 'tempDir/myTemp.txt' in
> >> >revision -1
> >>
> >> -1 == SVN_INVALID_REVNUM,
> >>
> >> But thanks for the report, I too think it should have reported the
> >> transaction name.
> >
> >I've addressed this on trunk in r22772.
> Dan,
>
> Just curious question to understand the Subversion development process.
>
> Pls. ignore this mail, if a valid ticket is already available in
> Subversion ug-tracking system.
Nope, nothing in the 'ug-tracker. :-P
> In this case, problem was reported by Alexander and you had fixed it
> in subsequent revision. Is it common practice in Subversion project to
> open new tickets on behalf of those who report problems, incase, if
> they have not done so ?
We don't typically open a bug report for an issue which has been
fixed, no. Personally, I wouldn't mind if a bug report was opened
against the relevant release, the rev number where the problem was
fixed was recorded, and the bug report was closed against target
milestone 1.5. I've found this process to be a useful tracking system
for those who come after, since it provides a higher level view of
what's been fixed than the change log messages, and is often available
before the CHANGES file or release notes.
- application/pgp-signature attachment: stored
Received on Wed Dec 20 18:37:59 2006