Hi! I have found the bug: The working copy was checked out using version 1.6.x that used svn:externals to check out the externals. Later on this working copy was upgraded using TortoiseSVN to the format used by version 1.7. It looks like this "upgrade" did not fully upgrade the externals. I have deleted the externals and checked them out using "svn update" again. Now things work.
- Matthias Meixner Von: Bert Huijben [mailto:b...@qqmail.nl] Gesendet: Freitag, 1. Juni 2012 11:16 An: Matthias Meixner; users@subversion.apache.org Betreff: RE: svn status leaves out changes in externals Hi, Did you create the externals by using 'svn checkout' or did you create 'your own externals' by checking out a separate working copy and assumed Subversion would just use it as an external? Svn status works correctly for me when I bring in externals using 'svn checkout' or 'svn update'. Bert From: Matthias Meixner [mailto:matthias.meix...@verifone.com]<mailto:[mailto:matthias.meix...@verifone.com]> Sent: vrijdag 1 juni 2012 10:37 To: users@subversion.apache.org<mailto:users@subversion.apache.org> Subject: svn status leaves out changes in externals Hello! In all versions up to 1.6.x "svn status" used to list all changed files including those found in directories referenced using svn:externals. Using version 1.7.5 this is not the case any longer. Even with option --depth infinite, changed files are not listed. I consider this a bug since it is not possible any more to recursively check for changed files, instead now I have to manually check all subdirectories one by one. Regards, Matthias Meixner ________________________________ This electronic message, including attachments, is intended only for the use of the individual or company named above or to which it is addressed. The information contained in this message shall be considered confidential and proprietary, and may include confidential work product. If you are not the intended recipient, please be aware that any unauthorized use, dissemination, distribution or copying of this message is strictly prohibited. If you have received this email in error, please notify the sender by replying to this message and deleting this email immediately.
