On Sat, Jan 12, 2013 at 9:12 AM, Raghu GS <raghugs_at_gmail.com> wrote:
> Thorsten Schöning <tschoening <at> am-soft.de> writes:
>
>>
>> Guten Tag Raghu GS,
>> am Samstag, 12. Januar 2013 um 11:51 schrieben Sie:
>>
>> > svn:external can only function in a working copy.
>> > How do implement the same in svn source.
>> > Because people may not check working copy.
>>
>> svn:external is something which needs to be recognized by the client,
>> it doesn't necessary need a working copy. For example TortoiseSVN has
>> a repo browser which shows svn:external definitions with a link icon
>> and is able to follow those without checking out a working copy, just
>> by double clicking. There's no such thing like implementing it in "svn
>> source" or a working copy, you always need a client to access the
>> repo and svn:externals are always part of the repo. How they are
>> recognized may be different depending on the clients.
>>
>> Mit freundlichen Grüßen,
>>
>> Thorsten Schöning
>>
>
> Hi Thorsten
>
> Thamks for your reply.
> I am receiving "Not a working copy" error in svn while creating
> external reference in svn.
>
> Isn't that mean external requires working copy?
> I am 100% sure that the folder in which i was trying to create
> the external reference are svn repositories, i even committed
> some code in it.
>
> Still i am getting the error said above,
> If svn doesn't require working copy, then assist me in
> resolving the issue.
I think that Thorsten perhaps misunderstood your problem. I just
tested this with Subersion 1.7.8 on a local file based repository, and
when you're trying to *set* svn:externals, you do need a local working
copy of the directory you're setting svn:externals for. TortoiseSVN
does provide wonderful views into the existing upstream repository and
its configurations, but I'm sure does not allow *directly* setting
these properties in the repo itself, because it's not in the basic
"svn" command itself.
Received on 2013-01-12 16:43:21 CET