Hi Neels,
thank you for your answer, but I can confirm that other commands
(i.e. svn update) do step into external folders, even in the latest
version ;)
Does anyone else have any suggestion?
Thanks a lot,
Max
On Fri, 12 Mar 2010 17:50:21 +0100
neels <neeels_at_gmail.com> wrote:
> On 12 March 2010 15:03, Max <iprmaster_at_gmail.com> wrote:
> > Hi,
> >
> > I have a repository with a structure which mixes some normal and
> > external repositories as follows
> >
> > - code_dir
> > |
> > `- src_dir
> > |
> > `- external_1
> > |
> > `- dir_1
> > |
> > `- external_2
> >
> > where code_dir, src_dir and dir_1 are located on a repository under
> > my control, while external_1 and external_2 are defined by means
> > svn:externals keywords.
> >
> > I have noticed that old svn versions were able to track down
> > modified files both in dir_1 and external_* directories. The last
> > version (I am running
>
> AFAIK subversion never stepped into externals folders, did it? If you
> want an svn command to run in the externals folder, you have to step
> into it (or supply it on the cmdline explicitly)
>
> ~Neels
>
> > 1.6.9) completely ignores external_1 and external_2 and give a list
> > of modified files located in dir_1 only. If I run "svn diff
> > code_dir/src_dir/external_1" I am able to see the list of modified
> > files in that directory too, of course.
> >
> > I know I am missing something trivial, but what? I have not found
> > any hint in the svn book...
> >
> > Thanks in advance for your help,
> > Max
> >
Received on 2010-03-13 12:19:40 CET