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

Language mix

From: Oddvar Kloster <Oddvar.Kloster_at_sintef.no>
Date: Thu, 2 Sep 2010 10:21:40 +0200

You may have noticed that the patch in may last post contains a bit of Norwegian language. This happens even though I currently have English as the selected language in TSVN. The GUI is all in English, but I can get a mix of English and Norwegian texts in update/merge/commit progress dialogs, apparently especially if some error or warning is propagated up from deeper parts of svn.
Any ideas on why this happens?

I can’t tell exactly how I arrived at this -- I’ve been through some sequence of en/no language switches and nightly upgades, and the ‘no’ language dll may have been a mismatch at times. Using latest full nightly.

Oddvar

From: Oddvar Kloster [mailto:Oddvar.Kloster_at_sintef.no]
Sent: 14. april 2010 15:32
To: dev_at_tortoisesvn.tigris.org
Subject: Re: Working copy node attached at wrong place in revgraph

> >The attached image shows the revgraph of a repository where I deleted and
> > then recreated a tag from a later revision. The working copy is updated to
> > the new tag version. But instead of marking the new tag node as the working
> > copy, the revgraph shows the working copy as a separate node attached to
> > the deleted version of the tag.
> >
> >Using latest nightly.
>
> Thanks for the report! Fixed in r18974.
>
> -- Stefan^2.

Thanks. However, now a different problem appears. In the attached figure, the working copy is updated to r633 on the 1.0.24 tag. But the revgraph shows the working copy as being on trunk.

Cheers,
Oddvar

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=2654448

To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-09-02 10:34:46 CEST

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.