[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Non-modified item listed as modified - remote revision issue?

From: Ben Fritz <fritzophrenic_at_gmail.com>
Date: Thu, 20 Nov 2014 10:11:44 -0600

On Wed, Nov 19, 2014 at 2:15 PM, Stefan Küng <tortoisesvn_at_gmail.com> wrote:

> On 18.11.2014 14:32, weie wrote:
> > Hi,
> >
> > I have a project repo in which I include part of a "core" repo as an
> external item. In this particular case I am including a branch of the core
> repo, specifically dedicated to the project.
> >
> > The project is uses explicit revisions of the external (operative rev).
> >
> > Now, I have made and committed a change in the branch of the core repo,
> then updated the project repo externals definition to the corresponding
> operative revision.
> >
> > Everything looks fine and dandy, and all files are of the correct
> revisions. Project working copy (and its externals) are all updated.
> >
> > This is my issue: if I on the root of the project working copy do a
> "check for modifications / check repository" it lists the newly committed
> core project changes as modifications. If I diff, there are no
> modifications, and there is nothing to commit.
> >
> > 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.
> >
> > If I at this point checkout a pristine working copy the issue goes away
> - no modifications are listed.
> >
> > Since all the files are actually correct this is not a critical issue,
> but a bit of an annoyance as the "check for mods"-window gets cluttered
> with a bunch of items which aren't changed.
> >
> > Any suggestions on how to resolve it would be appreciated (or hint on if
> I'm doing anything wrong) - I'm not too keen on having to pull out pristine
> w-c:s all the time.
> 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?


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2014-11-20 17:12:17 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.