On Thu, Nov 20, 2014 at 12:40 PM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:
> On 20.11.2014 17:11, Ben Fritz wrote:
> >
> > On Wed, Nov 19, 2014 at 2:15 PM, Stefan Küng <tortoisesvn_at_gmail.com
> > <mailto:tortoisesvn_at_gmail.com>> wrote:
> >
> > On 18.11.2014 14:32, weie wrote:
> > > Hi,
> > >
> > >
> > > The only discernible difference I can see is that the "remote
> revision" of the recently committed external item is older than the
> "revision". Clean-up of the working copy does not help the issue.
> > >
> > That's a known problem, but not something that will be fixed (I
> think):
> > I've reported this before on the svn mailing list, but the devs there
> > think that this is the correct behavior for an 'svn st -u -v', which
> is
> > what the "check repository" button does in the the
> > check-for-modifications dialog.
> >
> >
> >
> > Is there a workaround? "svn update" perhaps?
> >
>
> Not that I know of, no. The only way to avoid this is to not use pegged
> externals but have the externals point to HEAD.
>
>
>
Strange, because I don't recall running into this issue, and I use pegged
externals.
Perhaps it is because when I make changes to the external item, I
temporarily set the external to HEAD?
Or perhaps, deleting just the external item and doing an update to get it
back helps? I need to do that sometimes for other reasons.
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3091616
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2014-11-20 19:47:31 CET