Recommended Posts

A new version of TortoiseSVN has been released

A Subversion client, implemented as a windows shell extension.

TortoiseSVN is a really easy to use Revision control / version control / source control software for Windows.

Since it's not an integration for a specific IDE you can use it with whatever development tools you like.

TortoiseSVN is free to use. You don't need to get a loan or pay a full years salary to use it.

Notes:

Culminating over 9 months of development effort, this is the best release of TortoiseSVN yet, and delivers powerful features, including:

* Early support for tree conflict detection

* improved revision graph

* ...and many more.

Changes:

Version 1.6.0

  • NEW: Ignoring of multiple selected items by their extension. See issue #423 for details. (Stefan)
  • NEW: The log dialog allows filtering by bug-ID. See issue #422 for details. (Stefan)
  • NEW: Column to show the remote revision in the CfM dialog. (Stefan)
  • NEW: The current revision of the working copy item is shown in bold in the log dialog. See issue #425 for details. (Stefan)
  • NEW: The custom tsvn: urls allow a revision to be specified after the real url, separated with '?'. (Stefan)
  • NEW: The state of the 'merge non-interactive' checkbox is remembered across sessions. (Stefan)
  • NEW: editing the author in the log dialog is now possible for multiple selected revisions. (Stefan)
  • NEW: Paste command to paste copied/cut files from explorer into a working copy. See issue #427 for details. (Stefan)
  • NEW: TortoiseProc returns now 0 after the command finished successfully and -1 if the command failed with an error. See issue #426 for details. (Stefan)
  • NEW: Added blame command to context menu of the status list control. (Stefan)
  • NEW: "up" button in the repo browser. (Stefan)
  • NEW: Checkbox to exclude the externals in the Check-For-Modifications dialog. (Stefan)
  • NEW: Ability to cancel the "patch all" function. (Stefan)
  • NEW: Option to disable the context menu for specific paths. (Stefan)
  • NEW: Extended the IBugTraqProvider. See issue #428 for details. (Stefan)
  • NEW: The status cache handles "runas" now better. (Stefan)
  • NEW: Automated removal of unused log caches. (Stefan Fuhrmann)
  • NEW: When diffing against BASE, the diff tool now shows the BASE revision in the view title. (Stefan)
  • NEW: if "unversioned files mark parent folder as modified" is active,
  • the revert dialog shows a hint if unversioned files are found. (Stefan)
  • NEW: Auto-maintenance for log caches plus several settings to control its behavior. (Stefan Fuhrmann)
  • NEW: Log cache supports multiple repositories with the same UUID. (Stefan Fuhrmann)
  • NEW: Revision graph settings page. Several previously hidden features are now available to the user. (Stefan Fuhrmann)
  • NEW: The status list control shows the entries grouped by externals if no changelists are present. (Stefan)
  • NEW: two project properties (bugtraq:provideruuid and bugtraq:providerparams) to specifiy the IBugTraqProvider for the project. (Stefan)
  • NEW: Helper dialog to resolve property conflicts. (Stefan)
  • NEW: Revision graph can be collapsed / expanded as well as split and joined. (Stefan Fuhrmann)
  • NEW: Helper dialog to resolve tree conflicts. (Stefan)
  • NEW: TortoiseBlame shows the revision range in the title. See issue #429 for details. (Stefan)
  • NEW: Revision graph: Option to hide unmodified branches (Stefan Fuhrmann)
  • NEW: Revision graph: Option to show workspace modifications as extra node (Stefan Fuhrmann)
  • NEW: Revision graph: Update / Switch WC in node context menu (Stefan Fuhrmann)
  • NEW: A warning is shown if the user tries to add a file that was versioned but renamed in case. (Stefan)
  • NEW: TortoiseMerge scrolls the views automatically when selecting with the left mouse button down. (Stefan)
  • NEW: In the log dialog filter, a ! char at the beginning will negate the filter string. (Stefan)
  • NEW: Column in the check-for-modifications dialog to show the lock date. (Stefan)
  • NEW: Context menu to delete and ignore files at the same time. (Stefan)
  • NEW: Tooltips in the action column of the log dialog, explaining the action icons. (Stefan)
  • NEW: When moving/copying a file over an existing file, ask the user whether to replace that existing file. (Stefan)
  • NEW: Shift-click feature for merge tools. See issue #430 for details. (Stefan)
  • NEW: "Create patch" and "Check for Modifications" available from commit/CfM dialog. (Stefan)
  • NEW: new column for checkout depth in the CSVNStatusListCtrl. (Stefan)
  • NEW: overlays in the CSVNStatusListCtrl for the different depths and external/nested files and folders. (Stefan)
  • CHG: The bug-ID column width in the log dialog is now limited to 200 pixels. (Stefan)
  • CHG: The right-drag context menu now only shows "Export" if a versioned folder is dragged (for files, the windows 'copy' does the same). (Stefan)
  • CHG: The right-drag context menu checks whether source and target are from the same repository and shows the "SVN move" and "SVN copy" commands only if they are. (Stefan)
  • CHG: When only files are selected for "Add", the Add-dialog is not shown anymore but the files are added immediately. (Stefan)
  • CHG: file:// access to BDB based repositories is no longer supported. (Stefan)
  • CHG: the log dialog now shows a possible error message when fetching the log as a text in the top list control instead of showing a popup message box. (Stefan)
  • CHG: New revision graph look. (Stefan Fuhrmann)
  • CHG: Faster and more reliable revision graph filtering. (Stefan Fuhrmann)
  • CHG: If tsvn:logtemplate was set and not changed in the commit dialog, it isn't added to the log history anymore. (Stefan)
  • CHG: "Ambiguous URL" option no longer limits log cache functionality. (Stefan Fuhrmann)
  • CHG: Various improvements to log statistics graphs (Aras Pranckevicius)
  • CHG: The merge wizard is now resizable. (Stefan)
  • CHG: The checkout/export dialogs do not ask whether to create the folder to checkout/export aynmore but silently create it. (Stefan)

Download here

Link to comment
https://www.neowin.net/forum/topic/749984-tortoisesvn-160/
Share on other sites

The blame viewer appears to no longer work correctly in this version.
Bug is fixed for the next version...
Version 1.6.1

- CHG: The history dialog is now 'attached' to the commit dialog. (Stefan)

- BUG: Showing properties from the explorer svn properties tab did not work

if a language other than English was set. (Stefan)

- BUG: Crash in "cleanup". (Stefan)

- BUG: TortoiseBlame did showed only empty files. (Stefan)

I guess you'll have to wait for them to release it (or compile it yourself).

EDIT: TortoiseSVN-1.6.0.15897-dev-win32-svn-1.6.0.msi is available from here (nightly branch builds). Should contain the fix.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • My father still uses a programme written in dbase3. Still manages to work with a little help from dosbox. 
    • Microsoft hides these secret Windows 11 performance boost settings available on every PC by Sayan Sen Windows enthusiasts often look for ways to extract as much performance out of their systems as possible, and it's often the case that they try and do so while trying to minimize the heat and power consumption. This is especially relevant in the case of mobile Windows PCs since laptops and notebooks tend to get hot and management of that heat and power is harder in such a form factor. As such users often turn to techniques like under-volting which can be used to squeeze out the maximum capabilities of a chip while also maintaining lowered power levels. There are official apps from AMD and Intel with the likes of Ryzen Master and XTU (Extreme Tuning Utility). While these are quite handy, most enthusiasts probably prefer to dig into the BIOS and play around with settings there like Curve Optimizer on Ryzen, which lets users set various frequency-voltage scaling values. These are essentially called P-States. If you are not familiar with them, Processor Power Management is done through Advanced Configuration and Power Interface (ACPI) P-states and C-states. While P-states or performance pwoer states handle CPU voltage-frequency scaling, C-states deal with CPU sleep states so that some of the CPU functions, which are not necessary at that moment, can be disabled. The P-states and C-states work together to make the processor run more efficiently. It helps the OS and apps determine which cores can be parked and which should be boosted. Of course not every user is an enthusiast or knows the technicalities and integrities of how things like overclocking or undervolting work. Thankfully for them Windows itself offers something pretty cool, though it is hidden by default on all systems. By default, Windows only has two P-States, "Minimum Processor State" and "Maximum Processor State." However, this can be changed with a Registry trick to expand the options under a secret "Processor performance boost mode" dropdown. This essentially enables the HWP or hardware P-States available on a device, and these are not controlled just by the OS itself as the underlying hardware gets involved too. In total there are five Processor Performance Boost Mode profiles that control how Windows requests and allows CPU turbo/boost behavior under the different power policies. They are: Disabled: In this mode, processor boosting is effectively turned off. The CPU will avoid entering turbo or boost frequencies and instead operate closer to its base frequency ceiling. This can significantly reduce power consumption and heat output, but at the cost of reduced burst performance and responsiveness in short workloads. Enabled: This is the standard behavior where boost functionality is allowed under normal conditions. The processor can opportunistically increase frequency when workload demands it, balancing performance gains with power and thermal constraints as managed by the system. Aggressive: Aggressive mode favors performance more heavily, allowing the CPU to enter higher boost states more readily and sustain them longer. This should in theory improve responsiveness under bursty or heavy workloads but increases power draw and thermal output compared to the default enabled behavior. Efficient Enabled: This mode still allows boosting, but with a stronger bias toward energy efficiency. The system attempts to use boost more selectively, avoiding unnecessary frequency spikes when the performance gain is marginal. Efficient Aggressive: This is a hybrid approach where boost is still performance-responsive, but the system continuously weighs efficiency more heavily than in Aggressive mode. It aims to deliver noticeable performance improvements while reducing wasted power in less demanding scenarios. Here's how to enable the Processor performance boost mode: Open Registry Editor: Press Win+R, type regedit, and click OK. Go to: HKLM\SYSTEM\CurrentControlSet\Control\Power\PowerSettings\54533251-82be-4824-96c1-47b60b740d00\be337238-0d82-4146-a960-4f3749d470c7 (where HKLM stands for HKEY_LOCAL_MACHINE_) Modify the value of Attributes from 1 to 2 (you can find modify option by right-clicking) After that, exit Registry, you should now be able to see the new "Processor performance boost mode" dropdown menu: As you can see there are now five new P-States or CPPC states or power profile available that help define the boost mode processor setting on your PC. Wrapping it up here's a quick run-down of the settings as defined by Microsoft itself. Setting Description Disabled The corresponding P-state-based behaviour is disabled. Collaborative Processor Performance Control (CPPC) behaviour is disabled. Enabled The corresponding P-state-based behaviour is enabled. CPPC behaviour is Efficient Enabled. Aggressive The corresponding P-state-based behaviour is enabled. CPPC behaviour is Aggressive. Efficient Enabled The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Efficient Enabled. Efficient Aggressive The corresponding P-state-based behaviour is Efficient. CPPC behaviour is Aggressive. Aggressive At Guaranteed Windows calculates the desired extra performance above the guaranteed performance level, and asks the processor to deliver that specific performance level. Efficient Aggressive At Guaranteed Windows always asks the processor to deliver the highest possible performance above the guaranteed performance level. In the next part we shall be comparing these settings to explore how much of a benefit or regression they can provide in terms of performance and power efficiency. If you decide to change the values on your system and are experiencing problems like crashes or an overheating PC, make sure to revert the steps back to the original state.
    • I think he means you haven't reviewed previous UFC games. Of course it doesn't matter... Every time you just report on something that involves the President even if just simply what happened you guys usually get accused of being anti-Trump. We live in fun times.
  • Recent Achievements

    • One Month Later
      Leroy Jethro Gibbs earned a badge
      One Month Later
    • Conversation Starter
      flexorcist earned a badge
      Conversation Starter
    • One Month Later
      AndreaB earned a badge
      One Month Later
    • One Month Later
      agatameier earned a badge
      One Month Later
    • Week One Done
      agatameier earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      518
    2. 2
      +Edouard
      198
    3. 3
      PsYcHoKiLLa
      147
    4. 4
      ATLien_0
      93
    5. 5
      Steven P.
      77
  • Tell a friend

    Love Neowin? Tell a friend!