gmane.comp.version-control.subversion.tortoisesvn.devel

Re: Migrating an SVN server to new machine

Stefan Küng — 2012-05-25T16:22:23

Please use the users list for asking such questions. The dev list is for 
developing TSVN, not users.

As for your problem: read the docs about "relocate".

Stefan

Migrating an SVN server to new machine

Nick Gilbert — 2012-05-25T15:59:43

Hi,
If we were to move a subversion server to a new machine, the URLs inside 
all the working copies would obviously have to change. Is there any way 
to just "fix" the server URLs inside the working copies or do we need to 
check out all the projects again after migrating the server to the new 
machine (for many reasons, we cannot name the new machine the same name 
as the old one).  I tried to open the wc.db file in an SQLite viewer to 
see if it was a simple setting but this file doesn't seem to open 
despite the fact it appears to be an SQLite 3 database.

Eg:
http://server1/svn/projectname/ >    http://server2/svn/projectname/

I realise now we should have a used a subversion specific URL for the 
working copies which would make moving the service much easier - like 
svnserver or something (the URLs are used internally only - hence lack 
of extension).

Many thanks,
Nick

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

Re: Automatic update & commit

Lorenz — 2012-05-24T06:22:06


There are in fact two seperate automatic modes.
One for commit and one for update.

And at least the commit part should be controllable by the server
administrator.

So perhapse there should be two properies:
tsvn:automatic-commit
andtsvn:automatic-update
both defaulting to 'off' and options 'per-user' and 'on'

the latter might be useful for automatic website updates or such.


If there are two properties, there should be two (sub)menu entries
too.
And menu entries could/should reflect the state.

I'm thinking about menu entries with a check mark on the left side.

If the related property is 'off' or 'on' the check box should reflect
the setting, but the menu entry should be grayed-out to indicate that
the user has no choice here.

In the 'per-user' setting menu entry would be displayed in the normal
colors and reflect the user choice.


In light of the restrictions regarding icon overlay slots I refrain
from proposing additional overlay icons 8-)

Re: Automatic update & commit

Jan Keirse — 2012-05-24T08:05:23

On Thu, May 24, 2012 at 9:09 AM, Hans-Emil Skogh <Hans-Emil.Skogh< at >tritech.se


Isn't the best option to  seperate automatic commit from automatic update?
I don't think there's a real need to forcefully disable automatic update
anywhere. And that allows it to easily disable/enable automatic commit
where needed.
Moreover I'm likely to use automatic update on at least 1 of my working
copies, but will most certainly not enable automatic commit anywhere (while
I do see that it can be usefull for many.)
Automatic commit does require automatic update, so another option would be
to have a menu option 'automatic mode' that opens a window where you can
set a checkbox for automatic update and if automatic update is enabled an
automatic commit is allowed than an additional checkbox could be made
sensitive.

Re: Automatic update & commit

Hans-Emil Skogh — 2012-05-24T07:09:45

...

Then add a third value "read only" that makes it possible to optionally use automatic mode, but restricted to read only? That is, it would prevent automatic mode from making commits, but not prevent it from making updates.


Just because it's not useful for open source projects that rely on a strict policy of who may commit to the repository doesn't mean that it isn't useful in other circumstances.


That would probably help somewhat. Coupled with a suitably worded confirmation dialog might be enough to stop accidental activation (and the hilarity that would ensue).


To be honest: I'm not very fond of the extended menu. (Because it is the menu that you get when holding ctrl when right-clicking, right?) It is so close to an easter egg that I wouldn't even wish it to my least favorite feature to be hidden there. :-)


How about making it possible to disable the automatic mode with a registry entry? This would (imho) be much worse than the per-project property, but would at least allow sysadmins to disabl

Re: Automatic update & commit

Stefan Küng — 2012-05-23T18:30:48

I don't think that's a good idea. Here's why: if you set that property 
and disable automatic mode, then you also disable this for all read-only 
users who just want to have the updated source.
Imagine an open source project setting that property....



Having the option to turn this on in the submenu, not as a top-level 
menu entry should be enough in my opinion.
If that's not enough, only showing the entry in the extended menu would 
help as well.

Stefan

Re: Automatic update & commit

Hans-Emil Skogh — 2012-05-23T07:25:15

...

I'd like to propose to add a new TortoiseSVN project property to be able to disable this functionality on projects/repositories where it's not desirable to use it.

I imagine that an accidental activation of automatic mode followed by some enthusiastic moving & editing could wreak havoc on a project in very little time without the user understanding what is going on.

The property could be called "tsvn:automaticmode" and the states could be "on" (always enable automatic mode for this project), "off" (never allow automatic mode on this project) or not set (default) which would indicate user choice.

...

When I think about it I'd even go as far as saying that automatic mode should probably be better disabled by default and have to be explicitly enabled in the settings dialog. For users that should use automatic mode a system admin could enable the mode for them.
The risk of accidental activation and the headache that would follow for some projects (SVN lacking obliterate and all) is... not a pretty pictu

Re: Automatic update & commit

Stefan Küng — 2012-05-22T20:09:18

don't forget to create a new issue for this first.

Stefan

Automatic update & commit

Stefan Fuhrmann — 2012-05-22T17:57:56

Hi all,

As you may or may not know I helped with the
implementation of the recently released EasySVN
client. The latter is an extension to TSVN, adding
automatic commit and update for selected working
copies plus some Assembla-specific features.

I would like to move the core automatic commit &
update code to TSVN to make it available to a much
larger user base.

How does it work?
- User must activate the function on some w/c
   path (not necessarily the w/c base) via context
   menu or as an option during c/o. Can be de- and
   re-activated via context menu at any time.
- It uses a daemon similar to TSVNCache to watch
   selected working copies and the respective repositories
   for changes.
- Detected local changes (new / missing / changed nodes)
   get committed automatically with some standard message.
- Updates get pulled in just the same and conflicts will be
   resolved automatically by renaming the conflicting file.
- Open files will be checked for to reduce the risk of
   conflicting file access.
-

Re: Log message formatting

Stefan Küng — 2012-05-22T19:17:39

Sorry, no. You can not change that format.
I've created issue #303 for this:
http://code.google.com/p/tortoisesvn/issues/detail?id=303

Stefan

Log message formatting

omickron — 2012-05-22T08:37:51

There's a good ability in Log Messages form.
When selecting 2 or more revisions, frame with commit messages contains all messages of the selected revisions, with special format.

For example,

"r651
Expample commit message of revision 651.
---------------------
r649
Expample commit message of revision 649.
---------------------"

But how can I change format of this text?
I would prefer another view:

"Expample commit message of revision 651. [from rev.651]
Expample commit message of revision 649. [from rev.649]"

Is there any way to change format of the log message frame when it shows logs of 2 or more revisions?

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

To unsubscribe from this discussion, e-mail: [dev-unsubscribe< at >tortoisesvn.tigris.org].

TortoiseSVN translation status report for r22932

Lübbe Onken — 2012-05-21T07:03:44

TortoiseSVN translation status report for r22932

==== Translation of trunk/Languages =======================================
                                 : User interface     : Manuals
Total strings                    : 2588               : 3030
Language                         : Status (un/ma)     : Status (un)
===========================================================================
Arabic (Egypt) (ar)              : 23% (1974/0)       : ---
Bulgarian (bg)                   : 95% (128/0)        : ---
Catalan (ca)                     : 76% (610/0)        : ---
Chinese, simplified (zh_CN)      : OK                 : 79% (628)
Chinese, traditional (zh_TW)     : OK                 : ---
Croatian (hr)                    : OK                 : ---
Czech (cs)                       : OK                 : OK
Danish (da)                      : 95% (109/0)        : ---
Dutch (nl)                       : 99% (2/0)          : 86% (401)
Finnish (fi)                     : 99% (1/0)          : 99% (12)
French (fr)

TortoiseSVN translation status report for r22922

Lübbe Onken — 2012-05-18T06:35:38

TortoiseSVN translation status report for r22922

==== Translation of trunk/Languages =======================================
                                 : User interface     : Manuals
Total strings                    : 2588               : 3030
Language                         : Status (un/ma)     : Status (un)
===========================================================================
Arabic (Egypt) (ar)              : 23% (1974/0)       : ---
Bulgarian (bg)                   : 95% (128/0)        : ---
Catalan (ca)                     : 76% (610/0)        : ---
Chinese, simplified (zh_CN)      : OK                 : 79% (628)
Chinese, traditional (zh_TW)     : OK                 : ---
Croatian (hr)                    : OK                 : ---
Czech (cs)                       : OK                 : OK
Danish (da)                      : 95% (109/0)        : ---
Dutch (nl)                       : 99% (2/0)          : 86% (401)
Finnish (fi)                     : 99% (1/0)          : 99% (12)
French (fr)

Announcing the release of EasySVN

EasySVN — 2012-05-17T15:43:10

Assembla is announcing the release of EasySVN, a free, open-source
Subversion client with unique features to make Subversion easier to use. We
just posted a 1.0 release for Windows and a beta release for Macintosh. You
can download them from http://assemb.la/EasySVN

EasySVN adds the following capabilities:

• Automatic update and commit mode. When this is selected, your subversion
working copy acts like Dropbox, gDrive, Skydrive, and related cloud file
systems. It has the advantage of being open source and portable, so you
have many options for the location and security of files. Because it’s
Subversion, it handles big files and repositories. This mode is useful for
graphical files from designers, and other files that aren’t code.

• Simplified operations to checkout, invite, and create repositories on the
Assembla hosting system. For example, selecting “Share on Assembla” on any
local directory will create a repository, add the files, and commit them,
in one operation.

• Free backend storage

Re: TortoiseSVN 1.7.7 released

Simon Large — 2012-05-17T13:06:58

Great work, Stefan. That's an impressive list of fixes, plus the fixes
within subversion itself :-)

I like the write up about crash-server too.

Simon

TortoiseSVN 1.7.7 released

Stefan Küng — 2012-05-17T12:25:53

Hi,

We're proud to announce that TortoiseSVN 1.7.7 has been released.
It is linked against Subversion 1.7.5

We fixed a lot of bugs in TortoiseSVN this time, mostly thanks to the 
many crash reports that were sent.

To improve TortoiseSVN even further we've also included a new crash 
reporting tool this time. Please have a look at our post about this new 
crash handler and how we use it here:
http://tortoisesvn.net/crashhandler.html

We recommend that you update to this version as soon as possible.
You can get it from our download page:
http://tortoisesvn.net/downloads.html

The changelog for this version:
Version 1.7.7
- BUG: Issue #233: Crash when closing the
        progress dialog. (Stefan)
- BUG: Issue #234: Crash in
        repo browser. (Stefan)
- BUG: Issue #235: Crash when reverting/deleting
        items from the status list control. (Stefan)
- BUG: Issue #236: link-style buttons in commit
        dialog register on non-captured mouseup. (Stefan)
- BUG: Issue #237: crash with invalid
        confi

Show diffs on a tag reports an error

Xu Hong — 2012-05-16T15:01:14

Hi

My TSVN version is TortoiseSVN 1.7.99, Build 22798 - 32 Bit -dev,
2012/04/16 21:55:02

when I want to see diffs on  svn_version.h  , I got an error .   look
at the image.

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

To unsubscribe from this discussion, e-mail: [dev-unsubscribe< at >tortoisesvn.tigris.org].

RE: [tortoisesvn] r22909 committed - recreate the 1.7.7 tag.

Garcia, Paula — 2012-05-15T12:22:36

Hi, does anyone have a general e-mail that I can have some details about the Tortoise SVN Addin for Visual Studio software?

Thanks, Paula

From: Lübbe Onken [mailto:luebbe.tortoisesvn< at >googlemail.com]
Sent: Tuesday, May 15, 2012 8:23 AM
To: dev< at >tortoisesvn.tigris.org
Subject: Re: [tortoisesvn] r22909 committed - recreate the 1.7.7 tag.

2012/5/15 <tortoisesvn< at >googlecode.com<mailto:tortoisesvn< at >googlecode.com>>
Revision: 22909
Author:   tortoisesvn
Date:     Tue May 15 03:18:36 2012
Log:      recreate the 1.7.7 tag.
http://code.google.com/p/tortoisesvn/source/detail?r=22909

Added:
 /tags/version-1.7.7

Nice, now the few new French translations will make it into the new release :)

--
Cheers
- Lübbe

--
Please help me get more space on Dropbox :)
https://www.dropbox.com/referrals/NTIwMzcxNjI5
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net  PGP Key ID 0x23F511AB

-----------

Re: [tortoisesvn] r22909 committed - recreate the 1.7.7 tag.

Lübbe Onken — 2012-05-15T11:23:10

2012/5/15 <tortoisesvn< at >googlecode.com>



Nice, now the few new French translations will make it into the new release
:)

TortoiseSVN translation status report for r22905

Lübbe Onken — 2012-05-14T11:18:30

Hi Folks,

here's the latest and greatest translation status report.

==== Translation of trunk/Languages =======================================
                                 : User interface     : Manuals
Total strings                    : 2588               : 3032
Language                         : Status (un/ma)     : Status (un)
===========================================================================
Arabic (Egypt) (ar)              : 23% (1974/0)       : ---
Bulgarian (bg)                   : 95% (128/0)        : ---
Catalan (ca)                     : 76% (610/0)        : ---
Chinese, simplified (zh_CN)      : OK                 : 79% (626)
Chinese, traditional (zh_TW)     : OK                 : ---
Croatian (hr)                    : OK                 : ---
Czech (cs)                       : OK                 : OK
Danish (da)                      : 95% (109/0)        : ---
Dutch (nl)                       : 99% (2/0)          : 86% (399)
Finnish (fi)                     : 99% (1/0)          : 9

Re: Delay in starting TMerge

Stefan Küng — 2012-05-07T18:56:36

Tested with all styles on now three computers, both here at home and in 
the office. But I can't see any delay here.

Since the Office styles don't show the delay for you but only others, 
and also mostly on remote desktop connections maybe it has something to 
do with RemoteFX?
http://en.wikipedia.org/wiki/RemoteFX

Stefan