does anyone know why this command does not work: svn copy --revision 6600
file:///var/svnroot/repos/BJ/trunk/SleuthProject ./SleuthProject. This is
the project that vanished in thin air.
GM
On Mon, Jun 8, 2009 at 11:01 PM, Gerard Marcel <men.makaron_at_gmail.com>wrote:
> I don't see any log after may 1 for the particular project. The logs
> about the project ends suddenly. Sorry, the command did work after removing
> the project name from the url. The verification reported no errors. Can
> this be a bug?
>
>
>
>
> On Mon, Jun 8, 2009 at 3:03 PM, Ryan Schmidt <
> subversion-2009b_at_ryandesign.com> wrote:
>
>> On Jun 8, 2009, at 12:18, Gerard Marcel wrote:
>>
>> On Mon, Jun 8, 2009 at 12:10 PM, Mark Phippard wrote:
>>>
>>> On Mon, Jun 8, 2009 at 12:03 PM, Gerard Marcel wrote:
>>>>
>>>> The log stops at May 1 then that is it. There is no deletion reference
>>>>> in
>>>>> the log. Something else may have happened, but I have no idea what it
>>>>> is.
>>>>> Is this even possible? Has anyone seen this before?
>>>>>
>>>>
>>>> I am guessing you ran the wrong command. You cannot take the option
>>>> against your WC. You have to run it on the repos URL. Something like
>>>> this:
>>>>
>>>> $ svn log -v -r '{2009-05-01}':'{2009-06-09}' http://
>>>> svn.collab.net/repos/svn
>>>>
>>>> Just replace the URL with the URL to the root of your own repository.
>>>>
>>>>
>>> I have been running the command against file:/// on the command line.
>>> That is not working.
>>>
>>
>> I can't think of a reason why it wouldn't work. If you use "svn log <URL>"
>> (and if you're using the file:///-based URL to your repository that should
>> be fine) then you should see the entire log of that part of the repository.
>> (Log messages relating to other parts of the repository above the URL you
>> specified will not be shown.)
>>
>> When you say "the log stops at May 1" do you mean there are no entries
>> before May 1 or no entries after May 1? If no entries before May 1, did you
>> on May 1 copy this item, and are you using the --stop-on-copy option to the
>> svn log command? Some clients such as TortoiseSVN do so automatically I
>> believe. If you don't want the log to stop on a copy, don't use the
>> --stop-on-copy option. If no entries after May 1, then the only way I could
>> imagine that to happen is if you were in fact running the log operation
>> against a working copy that had not been updated since May 1, and not on a
>> URL as above.
>>
>> Have you tried running "svnadmin verify" on the repository to make sure
>> Subversion at least thinks it's ok?
>>
>>
>
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=1065&dsMessageId=2360523
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-06-09 06:00:57 CEST