So is this is a known issue? Should I report it through some other
means or will one of the developers pick this up?
Also (to anyone) would appreciate any insight to the other part of my
post, thanks in advance ...
- Lawrence
Lares Moreau wrote:
>On Mon, 2006-02-06 at 19:20 -0800, Lawrence Bruhmuller wrote:
>
>
>>Yes, that would definitely explain the last thing I saw. Looks like a
>>bug to me, what do you think?
>>
>>
>
>It looks like a bug to me.
>
>[cc'd back to users@, <insert reply-to header comment here>]
>
>-Lares
>
>
>
>>Lares Moreau wrote:
>>
>>
>>
>>>On Mon, 2006-02-06 at 18:10 -0800, Lawrence Bruhmuller wrote:
>>>
>>>
>>>
>>>
>>>>So I thought I understood exactly what HEAD, COMMITTED, BASE, etc. all
>>>>stood for, how they behaved, particularly in relation svn log. Turns
>>>>out that I don't, and I am thoroughly confused. Please correct my
>>>>understanding if the below is incorrect.
>>>>
>>>>Looks to me like HEAD is a repository-wide variable. No matter where in
>>>>my working copy I go, HEAD is always the same, absolute latest in the
>>>>repos. Hence, if I do svn log -r HEAD in some subdirectory, I might not
>>>>get anything back if those files weren't touched as part of the single
>>>>HEAD revision.
>>>>
>>>>Seems like BASE works the same way (i.e. sometimes I get nothing, if I
>>>>get a revision it is always the same, assuming that I don't selectively
>>>>update my working copy).
>>>>
>>>>Now, COMMITTED seems like it varies depending on where I am. If I do
>>>>svn log -r COMMITTED in one subdirectory, I'll get a different revision
>>>>than if I do it in another directory, and the revisions returned did
>>>>indeed include at least one file from the directory. And these two
>>>>directories are updated to latest, as part of the same call to svn update.
>>>>
>>>>This is very confusing! I can't believe the documentation (that I've
>>>>found) doesn't call out this location sensitive behavior of COMMITTED,
>>>>if that is in fact the case.
>>>>
>>>>However, now I'm totally befuddled because I have a new directory
>>>>(something was just added and committed, nothing since) and svn log -r
>>>>COMMITTED gives me no results! So maybe my assumption above is flawed.
>>>>
>>>>
>>>>
>>>>
>>>Something like this? I don't know if it's a bug or not.
>>>
>>>+++
>>>lares@jarita test % svn log -r HEAD
>>>------------------------------------------------------------------------
>>>r3 | lares | 2006-02-06 20:11:46 -0700 (Mon, 06 Feb 2006) | 2 lines
>>>Added bar/
>>>------------------------------------------------------------------------
>>>lares@jarita test % svn mkdir some_dir
>>>A some_dir
>>>lares@jarita test % svn ci -m "Added some_dir/"
>>>Adding some_dir
>>>Committed revision 4.
>>>lares@jarita test % svn log -r HEAD
>>>------------------------------------------------------------------------
>>>r4 | lares | 2006-02-06 20:15:35 -0700 (Mon, 06 Feb 2006) | 1 line
>>>Added some_dir/
>>>------------------------------------------------------------------------
>>>lares@jarita test % svn log -r COMMITED
>>>svn: Syntax error in revision argument 'COMMITED'
>>>lares@jarita test % svn log -r COMMITTED
>>>------------------------------------------------------------------------
>>>r3 | lares | 2006-02-06 20:11:46 -0700 (Mon, 06 Feb 2006) | 2 lines
>>>Added bar/
>>>------------------------------------------------------------------------
>>>lares@jarita test % svn up
>>>At revision 4.
>>>lares@jarita test % svn log -r COMMITTED
>>>------------------------------------------------------------------------
>>>r4 | lares | 2006-02-06 20:15:35 -0700 (Mon, 06 Feb 2006) | 1 line
>>>Added some_dir/
>>>------------------------------------------------------------------------
>>>+++
>>>
>>>-Lares
>>>
>>>
>>>
>>>
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Feb 9 07:35:13 2006