Re: TortoiseProc.exe command line merge regularly asks for cleanup
one sure way to get errors that require a cleanup is to have the working copies stored on a network share instead of a local drive. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/bad935c6-5cfd-4b4d-aad0-b2cba78c5177n%40googlegroups.com.
Re: Commit issues
The path N:\ indicates a network share. https://tortoisesvn.net/faq.html#wconshare -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/e8fc7bb8-b2f9-4023-a7a7-34ee4601f8d1n%40googlegroups.com.
Re: "Ghost Commit Files"
right-click on those files, in the context menu select "break lock". -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/63b2a821-503d-40b5-b2b1-adf09bea8decn%40googlegroups.com.
Re: To not delete the pathfile
if you set the registry DWORD value HKCU\Software\TortoiseSVN\Debug to 1, then TortoiseProc will show a message box on startup with the command line. While that message box is shown you can make a copy of the pathfile. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/8806c902-b350-46ad-808c-c216cc3c0c04n%40googlegroups.com.
Re: SVN::GetRootAndHead
would it work if we do both?
rev = cachedProperties.GetHeadRevision(uuid, path);
if ((rev == NO_REVISION) || (m_err != nullptr))
{
svn_error_clear(m_err);
rev = cachedProperties.GetHeadRevision(uuid, url);
}
I don't have a setup ready to test this. At least it would be better than
before:
- if the path doesn't exist anymore, we try again with the root
- if root works, fine
- if root doesn't work either, it's no worse than before
Stefan
--
You received this message because you are subscribed to the Google Groups
"TortoiseSVN-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to tortoisesvn-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/tortoisesvn-dev/f0a0e607-cecc-45ac-94b5-0e3bd5a07946n%40googlegroups.com.
Re: Invalid Drive
So once when you installed TSVN before there was a H: drive. open an admin command prompt, type subst H: C:\ and try installing again. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/9d6dc26c-f104-4dc8-9a72-60a2cb85c21fn%40googlegroups.com.
Re: Commit and Update options not showing up on a Fresh Checkout
Where exactly is your working copy stored? If it's on a network share then go to Settings dialog->Icon Overlays->Drive Types. check all that apply to you. But the better solution would be to store the working copy on the local drive. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/14643257-3b23-4711-a772-54dab5a39b10n%40googlegroups.com.
Re: Report of Properties
check for modifications-dialog. check the boxes (bottom left) - Directories - Unmodified - Properties now this may take quite a while. But after the dialog has fetched all data, you can right-click on the list contrl header and see all possible properties. Select the one you seek and you'll get a column with that property. Sort by that column and you'll get all files/folders with that property at the top, with all the property values shown in the column. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/3fb3ed96-0cee-45bd-95b5-856a7170ad31n%40googlegroups.com.
Re: Feature: Specify revision for external reference in creation of branch/tags
when you check the box, the revision is used at which those externals currently are at. Because that's the current state. Why would you need another revision? -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/76f8abd4-8759-4f69-8a29-9f14cf8cf79bn%40googlegroups.com.
Re: Feature request: distinguish between disconnect to server and to proxy
you have to ask for such a feature on the svn mailing list: https://subversion.apache.org/mailing-lists.html -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/09fa6352-fe8c-4c9d-94ff-3cb90dec15f3n%40googlegroups.com.
Re: Authentication with client certification failed
which svn client did you use for testing? Try setting creating the registry DWORD value: HKCU\Software\TortoiseSVN\OpenSSLCapi to 0 after that, try again with TSVN. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/8f2a0833-cbab-4fa7-964e-0fef47ef556en%40googlegroups.com.
Re: TortoiseMerge.exe Trips Up On Spaces
The problem is not TortoiseMerge but Powershell. https://stackoverflow.com/questions/1673967/how-to-run-an-exe-file-in-powershell-with-parameters-with-spaces-and-quotes just use cmd.exe /c ... to run TMerge from a powershell console, or use titles that don't have spaces or colons in it... -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/fb6af966-8894-4bad-9f3f-8f72472719ffn%40googlegroups.com.
Re: In search of a single SVN Update/Commit/Merge diagram
the diagrams look ok to me. However I'm not sure if showing everything in one single diagram is the right way: For me this seems more complicated than using one diagram for every operation. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/69a83536-b09a-4c9c-837f-a75318f5f6cbn%40googlegroups.com.
Re: Windows positions and sizes
works fine for me here. try this: go to the settings dialog->saved data->Dialog sizes and positions->Clear maybe that helps. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/143f7d9b-74ae-4716-8128-a6352e6825e6n%40googlegroups.com.
Re: SVN::GetRootAndHead
no objections from me. The revision for the repo root is the same as for the path, but of course works for non-existing paths as well since the root is never deleted. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/d94c2d4b-aaba-43fa-8731-4aa9a52f3cfdn%40googlegroups.com.
Re: Nightly builds fail
I think the build machine might have the hiccups. When I check now, the 32-bit build succeeds, but a few language packs fail because* '..\bin\Release\bin\restext.exe' failed to start.* but the restext.exe must be ok because the language packs before that error are build correctly. The x64 build fails now because the TortoiseSVN32_static.dll and TortoiseStub32.dll are missing, however looking at the 32-bit build log those are properly built. Let's wait a few days, maybe the hiccups go away. Stefan -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/adfbef39-fb7d-45d5-a3cd-92749f20ba20n%40googlegroups.com.
Re: SVN Update issue
first, this is the developers list. You should ask your questions on the users list instead. As for your problem: make sure the other developer uses the same repo url and is on the same branch. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/84282a0c-2f09-44c7-b22c-f97400e04654n%40googlegroups.com.
Re: black background in commit window
go to settings->advanced, find the entry ScintillaDirect2D and set the value to false. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/16c1aeba-6016-4c86-bea7-a243193db07an%40googlegroups.com.
Re: TortoiseSVN checking are slow
first: svn status does not require a connection to the server. Unless you pass -u to check for server updates as well. A status check first compares the file dates and file sizes. If they have changed the file is considered modified. However if the file dates are different but the file sizes are not, then the whole file has to be read (and the base file as well) and compared byte-by-byte. So my guess: a lot of your files were saved without any real change in it (i.e. the modification date is different) but they're not really different. Try running a cleanup, that often can restore the last-modification dates on the files. If that doesn't help, a fresh checkout... -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/a6327ec9-5a1e-41fa-80d3-1db6f80c3f46n%40googlegroups.com.
Re: Potential resource leak with GetIconInfo usage
fixed in r29676. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/d8825d50-0c34-468c-9f4f-c4c363793bc8n%40googlegroups.com.
Re: TMerge 1.14.6 uses SetThreadDpiAwarenessContext
TSVN does not support OS versions that are not supported by MS. Never has, never will. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/d0ed164c-ecf2-4e4e-a34d-1b25bc2797a0n%40googlegroups.com.
Re: Hello can anyone help with this error?
first, onedrive is NOT the place you should store your working copy, because onedrive does not keep the files fully present locally. This can (and will, trust me) interfere with almost all svn commands. second: the error seems to be an SSL problem. Make sure your server is up to date and can handle current encryption standards because old and insecure ones got removed from TSVN. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/c4d2467c-21e5-4574-933c-d1cf00ad37fdn%40googlegroups.com.
Re: Newbie - checkout Batch file works, Powershell version does not - why?
Create the registry DWORD value HKCU\Software\TortoiseSVN\Debug and set its value to 1. Then TSVN will show you the command line that was passed to it on every start. This might help you debug the problem. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/1b3d19b9-880c-4c4c-93d4-0958c723fed5n%40googlegroups.com.
Re: Drop translated documentation
On Sunday, December 3, 2023 at 10:09:32 PM UTC+1 daniel.l...@gmail.com wrote: Thanks for going ahead with this, I've checked and all looks good to me. I updated build.txt as well. A few nits: r29640 removed the call to unix2dos from doc.build. I can't find it being used elsewhere, unless I'm missing something we could probably remove that EXE from the repo. r29641 removed the includes of translations-docs.html except for one instance in the support.zh.html. Was that intentional? I can find no other reference to that file so if the last include is removed, the file can probably go as well. thanks for noticing. Fixed in r 29651 -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/3915ecea-f332-48b5-84de-5c7a337f1ce3n%40googlegroups.com.
sorry for the spam
I don't know how, but an asshole got itself to be a member of this group and posted spam. The asshole is banned now, and I hope it won't get another way to do its shit. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/69245d4a-70ca-4cf4-aac8-5b2121bbd421n%40googlegroups.com.
Re: Drop translated documentation
On Monday, November 20, 2023 at 10:56:49 AM UTC+1 daniel.l...@gmail.com wrote: Hi, A little over two years ago Stefan sent a message on the user list [1] about usage of the translated documentation. It only got a single response (from me). The translation of the documentation is done using a Python2 script with a script that seems obsolete (xml2po, depending on an external library libxml that doesn't seem to exist in Python3). It is non-trivial to rewrite the script to Python3 using the available XML processing modules (etree, minidom, sax). This script keeps us from migrating the build tool chain to Python3. Since there seems to be limited interest in the translated documentation, I'm proposing: - To drop translated documentation from the build scripts. - To delete the translated docs from the repository: Languages/[langcode]/TortoiseDoc.po and doc/images/[langcode] comes to mind, possibly others. doc/xsl/[langcode] - To remove the "Manual" translations from Transiffex - To reorganise the website and move the translated manuals to a separate "translated manuals for older versions". I suggest to update the website with the next release. No need to remove the translated docs now between releases. And once that's done, don't forget to migrate to python3 :) -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/0a7942fe-6033-4d60-8d4d-8d86cad426can%40googlegroups.com.
Re: r29635
On Sunday, November 19, 2023 at 8:19:02 PM UTC+1 daniel.l...@gmail.com wrote: Nit, but why the added ) in line 794 of /trunk/src/SVN/SVNStatusListCtrlHelpers.cpp? That's an accident ;) -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/20450d1e-4ea4-42ce-b905-5694378b648cn%40googlegroups.com.
Re: debugging TSVN in Visual Studio 2022
I wouldn't recommend debugging the shell extension part if you're not already familiar with shell extensions in general. While it is possible to do some debugging, getting everything set up for this takes a *lot* of time, and since you're dealing with the shell any mistake can basically break your system. What I would recommend is enabling the debug outputs the tsvn shell extension has built in: create a registry DWORD key under SOFTWARE\TortoiseSVN named DebugOutputString, and set the value to 1. Then restart the shell (reboot is maybe the safest and fastest way to do that). Then you can use dbgView from sysinternals (part of microsoft now) to see all the debug output of the tsvn shell extension. That might be enough to figure out the delay you have. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/ec53637c-4346-45c4-9357-18b5b5de9208n%40googlegroups.com.
Re: debugging TSVN in Visual Studio 2022
[image: Screenshot 2023-11-15 194517.png] -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/16362cb8-5199-4e14-9525-6bfd7bfbba8bn%40googlegroups.com.
Re: svn:externals link is not accepted if the local path contains an apostrophe
fixed in r29623 -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/4db8a0b1-76bc-4103-8553-52373310bc5an%40googlegroups.com.
Re: Wrong color in hook script error message
fixed in r29622 -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/ec615000-73c2-48ff-98ef-ffd99c0ec2can%40googlegroups.com.
Re: Question about Versioning-Scheme
On Thursday, November 2, 2023 at 11:43:12 AM UTC+1 Tuxedo Penguen wrote: Hi TortoiseSVN Devs I noticed that the TSVN releases are announced on the website according to a different versioning scheme than i have in the download and also in Registry. On the website on the newest Version i have: 1.14.5 (Major.Minor.Patch?) On the download i get: 1.14.5.29465 (Major.Minor.Patch.Build?) yes, that's the build number. After installation in the Registry (DisplayVersion): 1.14.29465 (Major.Minor.Build?) you can thank msi for that. You see, while msi does have four-number versions, the fourth number is completely ignored. That would not be a problem if we only had the official releases. But we also have the nightly build where only the build number increases. And if we would use the same versioning scheme for msi that would mean msi would not detect that the nightly build has a higher version than the already installed one. So for the msi (and what you call registry) we use Major.Minor.Build because the Build (actually the svn revision number) always increases, and thus msi can properly detect newer versions and do an upgrade. Stefan -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/4696b065-b68b-42ad-bed6-6570c61d1acen%40googlegroups.com.
Re: LanguagePack_1.14.5.29465-x64-de - Issues with ProductID / Product Code
the language packs are designed to not get uninstalled. The language dlls are uninstalled/removed when TSVN is removed or updated. There's no need to uninstall the language pack(s) separately. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/de78320f-2b88-4b6b-aea3-c00b199d0918n%40googlegroups.com.
Re: Repo browser cannot be opened
Settings dialog->saved data->Dialog sizes and positions->clear -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/55790026-0f73-464b-9e4b-92a0d39d1b37n%40googlegroups.com.
Re: Build instructions outdated?
On Tuesday, October 17, 2023 at 1:10:58 PM UTC+2 Stefan Sperling wrote: I am trying to build TortoiseSVN trunk by following the build instructions at https://sourceforge.net/p/tortoisesvn/code/HEAD/tree/trunk/build.txt I am stuck at this step during installation of dependencies: - libxml2 python bindings(\b 2) http://users.skynet.be/sbi/libxml-python/ The provided link no longer resolves. Where can I find an installation archive of this dependency? that link is still listed as the windows port: https://gitlab.gnome.org/GNOME/libxml2/-/wikis/Python-bindings so currently I don't have a working url either... The file build.txt also recommends installing Python 2.6, which I could manage to do by digging a bit. But since Python 2.6 is end-of-life, I wonder if using a newer version would work? Which version are TSVN developers currently using in practice? Still 2.6? I tried once to upgrade to a newer python version. I could make everything work with python3 with the exception of the xml2po.py file. And since that is a crucial part of the doc translation, I reverted everything back to python2.6. But I'm also considering dropping the translated docs and only leave the English docs alive. In that case we could update to python3. Stefan -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/3d3d4985-b4fa-4f1a-9d82-0a0517ce2100n%40googlegroups.com.
Re: Add additional information to the Windows Explorer Title Bar - SVN
just FYI: the feature in TGit was implemented by me ;) And of course I first thought of implementing this in TSVN first, but there are too many problems. As Daniel already pointed out the branch/trunk naming is only a convention. And yes, TSVN has "classification patterns" in the settings dialog under "Revision Graph" for exactly that. However, even with the classification done properly, showing a branch name in svn would still not be fully defined. Since you can have files within a folder point to another branch. Also, in Win11 the whole feature is obsolete, because there the explorer does not have a title bar anymore, doesn't show any text. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/93b62df7-9188-4106-b252-48a1d46733cfn%40googlegroups.com.
Re: [BUG] Multiple Windows-Explorer Tabs: Tortoise ContextMenu ignores currently active tab, but refers to the first tab always
On Wednesday, October 11, 2023 at 6:55:43 AM UTC+2 L KJ wrote: Hello, Any plan for the official release date? I still have this issue on the newest version(TortoiseSVN 1.14.5, Build29465) I was hoping that svn would make a new release first. But since that won't happen any time soon (or ever), I guess I'll have to make a new TSVN release without an svn release... So I'll do a new release soon. unless the svn devs decide to make an official release sometimes this century, then I'll wait. Stefan -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/da4cfbd7-0cb9-4af3-947e-0d2d72a2e4dcn%40googlegroups.com.
Re: 1.10.x EOL
On Sunday, September 24, 2023 at 10:48:20 AM UTC+2 daniel.l...@gmail.com wrote: On the Download page, there is a section on the "Context menu in file-open/save dialogs" there is a reference to Windows 7 / Windows 8. Do we still support those or should this section be removed? Well, that section applies to all 32-bit Windows OS. However Windows 11 does not have a 32-bit version anymore, but Windows 10 (and the server versions based on that) still do. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/016e28bf-7e80-48fb-b906-4638bfad87ebn%40googlegroups.com.
Re: CleanUp Does Not CleanUP
On Monday, October 2, 2023 at 2:01:27 PM UTC+2 Peter Conklin wrote: Stefan - thanks for following up. Here’s a snapshot of the error message. The temp file doesn’t exist in the folder so that’s what is throwing us. We actually “recreated” the file so it would be there, then ran a cleanup and still got the same error. Any further help would be appreciated. if a file inside the .svn folder is missing then cleanup won't help anymore. Only a fresh checkout will solve this. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/8df3a87a-9853-4c82-818f-b5ca94e82eben%40googlegroups.com.
Re: Icon overlay in the seperate "Status" column
No. Because that is only possible for "namespace" handlers, i.e. only for a single root folder like e.g. the onedrive folder. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/f4abffef-90cc-472b-a4f1-a394556015c5n%40googlegroups.com.
Re: Project Monitor: Update All doesn't update to latest version!
when updating multiple paths, TSVN tries to update all of them to the same revision, because there's a possible race condition when just updating to HEAD. Of course, TSVN only does that if all the paths to be updated are from the same repository. And that is checked by comparing the repository uuid. So, in your case it seems that both repositories have the same uuid - which can cause many problems, not just the one you're describing here. I mean it's called an UUID for a reason: it MUST be unique. use the 'svnadmin setuuid' command on one of the repos to change the uuid to something else, then do a fresh checkout. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/96746f50-a25d-41b6-81e3-c6bc6b665338n%40googlegroups.com.
Re: Nightly Build failures?
fatal error C1085: Cannot write precompiled header file: '..\..\obj\TortoiseMerge\Release64\TortoiseMerge.pch': There is not enough space on the disk. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/3ba7a0ad-5cab-4b30-a9bc-a353d82c9de4n%40googlegroups.com.
Re: how to get projectname in pre-commit hook
First, are you talking about client-side hooks (https://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-settings.html#tsvn-dug-settings-hooks) or server side hooks (https://svnbook.red-bean.com/en/1.8/svn.ref.reposhooks.pre-commit.html)? For client-side hooks, you get the CWD of the working copy, which you can then use to get the repo url or other info via e.g. the command line client or SubWCRev. For server side hooks, you get the path to the repository, which you then can pass to the svnlook utility to get all the info you need. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/8b499517-2df7-4973-a304-756d6be973acn%40googlegroups.com.
Re: r29609
Thanks for noticing. I fixed the url. Stefan -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/198f3009-1a03-4ef0-a4aa-832f533d7a60n%40googlegroups.com.
Re: Commit dialog - merge translated to start in German
Thanks for the report. I fixed the translation, will be in the next release. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/93d138bd-9cac-4dcc-a73f-2e2398d17a64n%40googlegroups.com.
Re: Compare Working Copy with Working Base for Unmodified file
There's a reason a temp file is created: the 'real' file might have svn:keywords expanded or might have other EOLs. SVN won't show such files as different from the ones in the repository. But they are different when passing them to a diff tool. So by default, the file to be diffed is first converted so that the keywords are removed and EOLs adjusted, that file is then saved to a temp file so it can be used by the diff tool. you can disable this behavior it it bothers you: settings dialog->Diff Viewer->convert files when diffing against BASE -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/1c9b4a26-0495-4d3d-b2cc-ff1697c6d032n%40googlegroups.com.
Re: Nightly Build failures?
I've now sent an email to 'it at wandisco dot com' since Ian hasn't replied for weeks now. Not sure this will help though... -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/40103cdc-182a-44a8-9d9d-066981401ec2n%40googlegroups.com.
Re: TortoiseSVN error when using revert command with "pathfile" option
remove the BOM in the revertpath.txt file. As stated in the docs: https://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-automation.html#tsvn-automation-basics that file must not have a BOM. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/b8afc370-ec77-4d36-9839-075cbf30663en%40googlegroups.com.
Re: [PATCH] Fix: TortoiseSVN (trunk) displays "fetching text bases" notifications incorrectly
committed your patch in r29607. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/3c35e2c3-8a3d-47b6-bbfc-1ff8e5c4dcd8n%40googlegroups.com.
Re: [PATCH] Fix: TortoiseSVN (trunk) displays "fetching text bases" notifications incorrectly
Thanks for the patch! After a first look I think this is great. I will do some testing first, but I think I'll commit your patch soon. Stefan -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/881ff3ee-a929-4696-ad17-16263c985558n%40googlegroups.com.
Re: [Feature Request] Windows Explorer Enhancement
https://tortoisesvn.net/faq.html#ovlremote -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/01d70025-b68a-4e84-abc2-638b38fd94c7n%40googlegroups.com.
Re: Merge fail and call to GenerateMergeLogMessage()
On Saturday, August 5, 2023 at 12:21:54 PM UTC+2 daniel.l...@gmail.com wrote: Prompted by the discussion in the users group [1], I've been investigating why the prompt to merge doesn't appear sometimes. When merging with a specified range, CSVNProgressDlg::CmdMerge() is used while merging without a range (or All revisions) is using CSVNProgressDlg::CmdMergeAll(). CSVNProgressDlg::CheckUpdateAndRetry() should check if an update is required: if (GetSVNError() && GetSVNError()->apr_err == SVN_ERR_CLIENT_MERGE_UPDATE_REQUIRED) ... prompt the user to update or cancel ... In CmdMerge, the call to GenerateMergeLogMessage() (line 3384) seems to reset the latest error (SVNBase::m_err) so GetSVNError() will return false. A naive fix would be to condition the call to GenerateMergeLogMessage() with if (!bFailed), however that is a direct revert of r27728 "Generate the merge log message even if the merge returned with an error: a merge conflict also returns an error.". I'm instead considering to check GetSVNError() and the actual error message but I don't have enough knowledge about the different error messages that could appear. I'm not against that, but in my experience that is hard to maintain. Because new errors are added frequently to svn, which means we'd have to keep up. Since the problem appears to be that GenerateMergeLogMessage() clears the current error, why not just do: auto oldErr = svn_error_dup(m_err); // do the GenerateMergeLogMessage part svn_error_clear(m_err); m_err = oldErr; Ideally, I'd like to do check for a list of error messages that indicate a merge failure and create a log message in these cases (it seems unneccesary to create a log message in case of a network failure). Unfortunately I don't know how to figure out this list of error messages. Another option would be to check for only SVN_ERR_CLIENT_MERGE_UPDATE_REQUIRED. That would solve the current bug but could open up for other bugs in the future if/when we want to look for other error messages later in the code. Any opinion on this? On a side note, CmdMergeReintegrate() (and CmdMergeReintegrateOldStyle() and CmdMergeReintegrateOldStyle()) should probably also be changed to run GenerateMergeLogMessage() in case of a merge conflict to give similar behaviour in all kind of merges. agreed. Stefan -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/7bb4e109-13bd-406d-8831-26eadf176b14n%40googlegroups.com.
Re: "Cannot merge into mixed-revision working copy" TortoiseSVN 1.14.1
using your screenshot, just marking something: [image: 2023-07-31 08_46_47-Merge.png] -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/e90e0efa-c080-4d4c-8890-b025279ef2dfn%40googlegroups.com.
Re: osdn.net longterm stability
On Friday, July 28, 2023 at 10:43:06 PM UTC+2 daniel.l...@gmail.com wrote: If there's anything I missed, just shout. Looks good I think. How about updating https://openhub.net/p/tortoisesvn? updated the url yesterday, but the status is still "Step 1 of 3: Downloading source code history (Waiting in queue)". Well, the stability of openhub is almost as bad as osdn.net :( I saw that the issue tracker is active. I have mixed feelings about issue trackers, they often tend to be a dump of things which no-one care about enough to fix. Maybe hide it in the menu? Done. Stefan -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/ee5a03d1-950b-4bb0-9090-e0910be0fa59n%40googlegroups.com.
Re: osdn.net longterm stability
website is updated, changes committed to the sf repository. sourceforge project also set active. If there's anything I missed, just shout. Stefan -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/d20f5788-1e29-45bc-9078-3b1df591b8abn%40googlegroups.com.
Re: osdn.net longterm stability
On Friday, July 28, 2023 at 4:24:21 PM UTC+2 daniel.l...@gmail.com wrote: Now even the OSDN Subversion repository seems to be offline (don't know if that was intentional or not). $ svn ls https://svn.osdn.net/svnroot/tortoisesvn/trunk svn: E170013: Unable to connect to a repository at URL ' https://svn.osdn.net/svnroot/tortoisesvn/trunk' svn: E02: Could not find the requested SVN filesystem yup, that was me. It seems you can't make the repo read-only without removing it from access completely. It seems that the repository on Sourceforge is already up to date: $ svn info https://svn.code.sf.net/p/tortoisesvn/code Path: code URL: https://svn.code.sf.net/p/tortoisesvn/code Relative URL: ^/ Repository Root: https://svn.code.sf.net/p/tortoisesvn/code Repository UUID: cc8e0003-5e82-43e2-9771-63201f7d8d9c Revision: 29592 Node Kind: directory Last Changed Author: danielsahlberg Last Changed Rev: 29592 Last Changed Date: 2023-07-07 12:24:13 +0200 (Fri, 07 Jul 2023) Shall we announce that all commits from now go to SourceForge? (Sorry for being explicit about that but I wanted to make sure we are all on the same page). I noticed that the repository UUID is different on SourceForge so some manual work is required to connect an existing WC to the new repository (delete .svn, checkout again). Yes, soon. I'm currently going through all html and code files to change osdn to sf where necessary and needed, then I'll update the website. Then we can announce the move. We then also need to switch the project status from "moved to" to "active". Will do. I can prepare to write something on the website. Shall we also in the same time look at migrating the website to SourceForge? Do you think it's necessary to announce this on the website? Just updating all links should be enough I think? Stefan -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/32d62ac5-d029-42af-88bc-5dc6fcbfb9c6n%40googlegroups.com.
Re: osdn.net longterm stability
So no objections to move everything (back) to sourceforge? If not, I'll first mark the osdn.net repo as readonly, then get the sf repo working and finally adjust all links of the website and everywhere else to sf. I think all people who have commit access to the osdn.net repo also have commit access to the sf.net repo? If not, give me a shout. Stefan -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/90714d3e-e8e5-42cf-b280-0b8a45fa58ean%40googlegroups.com.
Re: Nightly Build failures?
Well, my contact at WANdisco hasn't replied to any of my emails for three weeks now. Maybe he's on a long vacation? I'll wait another two weeks, then I'll start emailing random people at WANdisco... -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/60d9ff00-6892-4f57-8b12-5f2f3d1436f6n%40googlegroups.com.
Re: Downloading TortoiseSVN
I've uploaded all files that are on osdn.net to sourceforge.net, and I've also adjusted all links on the website to now point to the sourceforge downloads. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/848b3b6f-3179-4d9a-ba6a-d8a4d7efdd66n%40googlegroups.com.
Re: Tortoise SVN will not install in Win11
We're not responsible for WinGet. Download from our website and you'll be fine. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/89504975-035e-446c-aa91-483e0c44a1b1n%40googlegroups.com.
Re: osdn.net longterm stability
So we all know that osdn.net is basically dying, some parts are already dead. So we have to move somewhere else. I've tried contacting Ian at Wandisco several times, and I got no answer at all. Sure, it's holiday time, but it's been six weeks now without any answer. That means we won't get any help from Wandisco - considering the state of that company it maybe isn't a good bet either to move anything there. So that leaves sourceforge. I suggest to move both the repo and the downloads there, and then adjust the links on the website. But no rush: I don't expect another svn release for the next few years anyway, if ever. Stefan -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/217c7795-ef36-42b3-b851-07785889be7an%40googlegroups.com.
Re: SVN checkout issue
configure your virus scanner to exclude the working copy from being scanned. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/d07fde48-97e0-4893-af15-f8f4fb097da3n%40googlegroups.com.
Re: IPv6 Url with Special Characters
that makes no sense at all. How would TSVN know from an URL whether it resolves later to an ipv4 or an ipv6 ip address? -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/058ee7ce-a745-45eb-a20e-4972627713f0n%40googlegroups.com.
Re: "SVN Move/Copy and Rename versioned item here" in Windows Explorer no longer works
On Monday, July 3, 2023 at 4:54:14 PM UTC+2 Arnoud Berendsen wrote: *When MOVE is chosen in step 4:* TortoiseSVN shows the following error: "Subversion reported an error: Working copy [...] locked. [...] is already locked. Please execute the 'Cleanup' command. works fine for me. Tried on two systems (one Win10, one Win11) *When COPY is chosen in step 4:* After thinking about it for a few seconds, TortoiseSVN shows an error dialog reporting the following: "Subversion reported an error: sqlite[S5]: database is locked Additional errors: sqlite[S5]: database is locked Another process is blocking the working copy database, or the underlying filesystem does not support file locking; if the working copy is on a network filesystem, make sure file locking has been enabled on the file server. " Works fine for me too. So, is your working copy on an network share? -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/3bf12b7d-311e-4091-af45-17048443c9d7n%40googlegroups.com.
Re: bug in the manual
On Saturday, June 24, 2023 at 10:27:42 AM UTC+2 Mark Galeck wrote: I upgraded to the latest version of Tortoise and I am looking at the current manual available on your website. Running Windows 10 Pro. Chapter 1, Section "Checking Out a Working Copy" talks about the context menu TortoiseSVN → Checkout... There is no such menu item. Instead, it appears the item is "SVN Checkout..." I tried it and it seems that it works like what the manual says. Some menu items are shown on the top menu. There the menu text starts with "SVN ..." to indicate the origin. See here: https://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-settings.html#tsvn-dug-settings-main under "context menu settings". Since on your machine the checkout command is configured to show up on the top menu, the item is "SVN Checkout" and not in the submenu. -- Also, in the Section "Adding More Files", it says Right click on the folder and TortoiseSVN → Add In my humble opinion, it is not clear what "the folder" is. It should clarify: "the development folder". An inexperienced engineer would not be clear whether it is supposed to be the original project folder, or the development/checkout folder. The section title is "Adding More Files". You see the "More"? That makes it very clear what folder it is IMHO. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/7378bbeb-571b-4108-91d8-9dab387fc393n%40googlegroups.com.
Re: SVN icon issue
On Wednesday, June 21, 2023 at 6:48:42 PM UTC+2 Gaddam Nagarjuna wrote: *step 4* – As per your suggestion we are clearing the OneDrive cache from the Registry from this path ( Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\ShellIconOverlayIdentifiers ) ( This will fix the issue temporarily ) But end users are reaching back for a permanent solution. then reach out to microsoft and ask them to make OneDrive not reinstall the registry keys every few days... -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/dbe52ac5-1127-4572-924f-4a6f85d82f24n%40googlegroups.com.
Re: editorconfig built twice
On Sunday, June 18, 2023 at 9:23:06 PM UTC+2 daniel.l...@gmail.com wrote: It adds "only" about a second to the builds, but it seems unneccesary. May I suggest that we remove the target in ext\build\default.build? Sure, go ahead. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/b61553bf-271e-45fc-a773-1d1c7dbc2704n%40googlegroups.com.
Re: Nightly build crash on SVN Log with log cache enabled
On Saturday, June 10, 2023 at 6:27:59 PM UTC+2 daniel.l...@gmail.com wrote: I can reproduce this by: * deleting %appdata%\TortoiseSVN\logcache * doing Show log *and clicking a few different revisions* * Settings, Log Caching, Cached Repositories now show 4 items for the repository * repeating steps 2 and 3 seems to add 4 items to the list per iteration I still can't reproduce this. Also, I can't see why clicking on revisions in the log dialog would ADD something to the cache. I also don't see where this would even touch the cache? Another thing: The CRepositoryInfo::CData::Add() method is only called from code where a CRepositoryInfo::CData::Lookup() is called before. So it should not be possible to add entries that already exist. I'm out of ideas -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/7c6599a0-0a6d-4e1a-a11b-835e881e1fb3n%40googlegroups.com.
Re: Nightly build crash on SVN Log with log cache enabled
I had that situation too, then I added the logic that caused the crashes. But now I can't get it to show the duplicate entries anymore! I deleted my old cache. And showing logs for different repos just don't get me to where duplicate entries are shown. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/8ce4aaeb-44a4-4725-a945-36c344303022n%40googlegroups.com.
Re: Nightly build crash on SVN Log with log cache enabled
not sure, but maybe it has something to do with the version of VS that's used? I mean on the build server there's definitely not VS 17.6 installed... -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/57229554-b88f-412c-8c98-4071818c25can%40googlegroups.com.
Re: Nightly build crash on SVN Log with log cache enabled
you're right. The problem is the == operator. To work properly it would require to know the settings allowAmbiguousUrl/Uuid and act accordingly. While that could be done, it would make for very ugly code. I added the 'avoid duplicate' code because my local cache showed 10 entries for the same repo in the settings dialog. But maybe my cache was just corrupted. So I reverted that commit for now. If I ever get those multiple entries again, I'll try to come up with a solution that works. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/0cd407db-6755-4bae-9bf6-59cdf9d5dce4n%40googlegroups.com.
Re: Commit dialog setting so all files are checked by default?
there's no option to make TSVN auto-check unversioned files for a commit. In your case, I would recommend you write a check-commit hook script that runs an 'svn st' to check if there are unversioned items, then compare those to the list of checked items in the commit dialog and reject the commit if there are unversioned items that are not checked. https://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-settings.html#tsvn-dug-settings-hooks -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/ff84d9e5-ee8b-493b-b7ff-ede7485ea98cn%40googlegroups.com.
Re: Enable asm for OpenSSL
On Saturday, June 3, 2023 at 6:15:52 PM UTC+2 daniel.l...@gmail.com wrote: I can ask Ian to install nasm on the build machine, but I have no idea how long that will take. Could you maybe add a nant target that enables the asm build and still use no-asm if the nant target was not called? That way the nightly builds would still run through with no-asm. And users who don't have nasm installed can also build without changes. That is a good idea, although I'd rather prefer to make it asm by default and have a no-asm target since that matches the default in OpenSSL. We can always have the "schedule" target add the no-asm option good idea, haven't thought of the "schedule" action :) -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/93821da5-6403--b1be-74431878431dn%40googlegroups.com.
Re: Enable asm for OpenSSL
On Saturday, June 3, 2023 at 5:11:53 PM UTC+2 daniel.l...@gmail.com wrote: = --- ext/build/OpenSSL.build (revision 29575) +++ ext/build/OpenSSL.build (working copy) @@ -52,7 +52,6 @@ - ]]] I can ask Ian to install nasm on the build machine, but I have no idea how long that will take. Could you maybe add a nant target that enables the asm build and still use no-asm if the nant target was not called? That way the nightly builds would still run through with no-asm. And users who don't have nasm installed can also build without changes. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/67bf51f8-3281-4144-b1ea-408302f1850dn%40googlegroups.com.
Re: build.txt
never realized that VS2022 is not available in a 32-bit version. I only read that it finally is available as x64 version. So yes, that section can therefore be removed. But the 'cross' option when building is still necessary when building the ARM version. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/ce226309-56ff-4463-a3f0-cd26c2c77dacn%40googlegroups.com.
Re: osdn.net longterm stability
I'm aware of the problems with osdn.net for quite a while now. But unfortunately there are not many other options available anymore. Osdn.net was sold to a mobile app gaming company called Appirits, but since then it seems that osdn.net has been abandoned. Logan Abbott who owns sourceforge reached out to me a few times already, suggesting that I move TSVN back to sourceforge. But I haven't forgotten the desaster SF had when they moved everything to new servers. All data was lost, no backups available for most repositories! I was lucky I had a local svnsync of the TSVN repo, or we had lost everything. So while SF *now *seems better than osdn.net, I'm reluctant to move back there. Also, moving the repo also means a lot of work, that's not just done in a day... are there other options available besides sourceforge.net? Stefan -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/20e444a3-1fcc-478b-86a4-85776c15a5f9n%40googlegroups.com.
Re: Enable asm for OpenSSL
The reason for the no-asm option was that the asm code often (it felt like every other release) was broken. Either with the asm that comes with VS, or later with MASM as well: When they switched to requiring MASM I thought the build problems were solved, but the second version after the switch failed again. So I had enough and used the no-asm switch. Yes, the asm code is a little bit faster. But honestly the slightly reduced data throughput won't affect 99.99% of all users. Because even in your test with a 7GB file it 'only' took 50 instead of 17 seconds. And who has such files in an svn repository? Scale that test down to a size that might be used in a real setup, and you won't see a user-noticeable difference. Also, your test uses localhost, with a transfer rate of 425MByte/s - so not something you get even on very fast company LAN's. So for me, I'd rather keep using the no-asm flag. What bothers me more than using no-asm is that there's even such a switch available! While asm code could be necessary in certain situations for performance, it really is not necessary anymore today, at least not if the devs understand C/C++. Other libs that used asm code before got rid of that (or deprecated the asm code) in newer versions. For example zlib. So why is openssl still using asm code? So basically, I won't object if someone wants to enable the asm code in the build. But I myself won't do it. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/9ba200a1-b4e7-4ff0-acbd-052e451474e0n%40googlegroups.com.
Re: Nightly build crash on SVN Log with log cache enabled
and I still don't see the crash on my machine. Tried showing log for several working copies, single files in them. Even showed the log for urls instead of local paths. I don't get any crashes or error messages about illegal repo urls. Also deleted the whole log cache and tried everything again. Still, no crash for me :( -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/9f1a5daf-1e76-438a-839b-71ae693c2268n%40googlegroups.com.
Re: Nightly build crash on SVN Log with log cache enabled
I made a few changes to the log caching, but those changes are mostly refactoring. Unfortunately, I can't reproduce a crash of the error message on my machine here. Maybe you guys can debug the problem on your machine? -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/d24c4068-ec9f-4755-a37e-56ba5f51494fn%40googlegroups.com.
Re: [Feature Request] Cache merge commit logs
On Wednesday, May 3, 2023 at 3:08:03 PM UTC+2 T Z wrote: The log caching feature is really nice for speeding up the display of large logs. However, it doesn't appear to cache merge commit messages. Yes, merge commits are not cached with the log cache. Sorry, but that's by design. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/fbe5869f-4433-49d2-8e47-01853669f094n%40googlegroups.com.
Re: TortoiseSVN and JAMA
TSVN can work with any issue tracker. See the docs on how to integrate: https://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-bugtracker.html however if you mean TSVN fetching info from the issue tracker directly, that requires a plugin. But there's no plugin for JAMA issue tracker that I know of. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/09a12ff2-d3e5-41f7-93b5-c008877467f5n%40googlegroups.com.
Re: "Fetching Tree Conflict information" dialog during update stuck?
On Wednesday, May 10, 2023 at 9:28:49 AM UTC+2 Jens Christian Restemeier wrote: Hi, Sometimes after an update Tortoise SVN shows a "Fetching Tree Conflict information" dialog. I have never seen it complete whatever it is doing, even when leaving it sitting for a few minutes. What is it actually doing, and would it be possible to get some kind of status or progress information? I assume it downloads some changelists for past revisions, but that shouldn't take that long. As the dialog says, it's fetching tree conflict information. This means that the update caused a tree conflict which you have to resolve. To help you with resolving the tree conflict, svn tries to fetch additional information about that conflict. But it has to contact the repository to do so. Depending on the version of the svn server this can take a very long time. Of course, you can cancel that info-fetching. But then you have to figure out yourself why the tree conflict happend without additional info. And yes, most users won't need that additional info to resolve the conflict. Stefan -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/6d5c0b2e-20cf-4cc9-98f4-21028d2de52dn%40googlegroups.com.
Re: No nightly builds
I've mailed Ian, and he deleted the include folder and ran an 'svn up', so there should not be any more conflicts. But the build still fails... -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/7f665450-5cb5-4fa2-91ce-334b80c9d2e6n%40googlegroups.com.
Re: Updated dependencies for TortoiseSVN
Any objections to switch to 1.7.4? no objections at all! Stefan -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/2287f4af-3291-4aaf-94e3-470d9f68c83dn%40googlegroups.com.
Re: Updated dependencies for TortoiseSVN
yep, it's the new apr version. I'll go back to apr 1.7.2 - this needs to be fixed either in apr or the svn lib. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/86ce8f8d-7a22-4d7c-a150-3ce55709ba5en%40googlegroups.com.
Re: Updated dependencies for TortoiseSVN
Not sure if it has something to do with this, but now I get an SVN_ERR_FS_INDEX_OVERFLOW error on ever commit to a file:/// repository. Can't be the updated OpenSSL or serf, but maybe the APR one? .\svn.exe commit D:\Development\SVN\Tests\repospacewc --message="test" ⏱️0ms SendingTests\repospacewc\src\AboutDlg.cpp Transmitting file data .done Committing transaction... D:\Development\SVN\TortoiseSVN\ext\subversion\subversion\svn\commit-cmd.c:185, D:\Development\SVN\TortoiseSVN\ext\subversion\subversion\libsvn_client\commit.c:1097, D:\Development\SVN\TortoiseSVN\ext\subversion\subversion\libsvn_client\commit.c:156: (apr_err=SVN_ERR_FS_INDEX_OVERFLOW)svn: E160056: Commit failed (details follow): D:\Development\SVN\TortoiseSVN\ext\subversion\subversion\libsvn_client\commit.c:1003, D:\Development\SVN\TortoiseSVN\ext\subversion\subversion\libsvn_client\commit_util.c:1974, D:\Development\SVN\TortoiseSVN\ext\subversion\subversion\libsvn_repos\commit.c:867, D:\Development\SVN\TortoiseSVN\ext\subversion\subversion\libsvn_fs\fs-loader.c:885, D:\Development\SVN\TortoiseSVN\ext\subversion\subversion\libsvn_fs_fs\tree.c:2381, D:\Development\SVN\TortoiseSVN\ext\subversion\subversion\libsvn_fs_fs\transaction.c:3983, D:\Development\SVN\TortoiseSVN\ext\subversion\subversion\libsvn_fs_fs\fs_fs.c:368, D:\Development\SVN\TortoiseSVN\ext\subversion\subversion\libsvn_fs_fs\fs_fs.c:240, D:\Development\SVN\TortoiseSVN\ext\subversion\subversion\libsvn_fs_fs\fs_fs.c:228, D:\Development\SVN\TortoiseSVN\ext\subversion\subversion\libsvn_fs_fs\transaction.c:3912, D:\Development\SVN\TortoiseSVN\ext\subversion\subversion\libsvn_fs_fs\transaction.c:3489, D:\Development\SVN\TortoiseSVN\ext\subversion\subversion\libsvn_fs_fs\tree.c:4864, D:\Development\SVN\TortoiseSVN\ext\subversion\subversion\libsvn_fs_fs\tree.c:4729, D:\Development\SVN\TortoiseSVN\ext\subversion\subversion\libsvn_fs_fs\dag.c:275, D:\Development\SVN\TortoiseSVN\ext\subversion\subversion\libsvn_fs_fs\dag.c:167, D:\Development\SVN\TortoiseSVN\ext\subversion\subversion\libsvn_fs_fs\cached_data.c:533, D:\Development\SVN\TortoiseSVN\ext\subversion\subversion\libsvn_fs_fs\cached_data.c:471, D:\Development\SVN\TortoiseSVN\ext\subversion\subversion\libsvn_fs_fs\cached_data.c:228, D:\Development\SVN\TortoiseSVN\ext\subversion\subversion\libsvn_fs_fs\index.c:1799, D:\Development\SVN\TortoiseSVN\ext\subversion\subversion\libsvn_fs_fs\index.c:1587, D:\Development\SVN\TortoiseSVN\ext\subversion\subversion\libsvn_fs_fs\index.c:1491: (apr_err=SVN_ERR_FS_INDEX_OVERFLOW) svn: E160056: Item index 2 too large in revision 4 -- You received this message because you are subscribed to the Google Groups "TortoiseSVN-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn-dev+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn-dev/b1615642-8193-4e08-abf0-db931a8c7d6fn%40googlegroups.com.
Re: Tortoiseproc update with pathfile works, commit does not
Sorry, took me a while to figure this out since I couldn't reproduce it first. The problem is your txt file with the paths in it: there are empty lines in it! Remove all the newlines after the path and you should be fine. Stefan -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/00a4d1b6-5d92-4947-b9aa-7bee61435b15n%40googlegroups.com.
Re: Tortoiseproc update with pathfile works, commit does not
On Thursday, April 6, 2023 at 2:05:00 PM UTC+2 ne...@medina-electronics.co.uk wrote: Windows 11 platform, Tortoise 1.14.99 Build 29538 I have written a script using command:update /pathfile pointing to a file which has a list of paths to folders to update, this works as expected. If I copy the the same script and use command:commit instead of update, it does not work. The GUI opens with the list of paths but on pressing OK I get a Commit fail message with the Error Message " is not under version control" If I try a single line commit using /path:"" it does work. is of course appropriate to each folder, such as C:\MEDC\CorporateDocs\trunk\ You can not commit multiple paths if they're not *all *inside the *same *working copy. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/c858aab0-e198-407b-ac21-b65dfaf71e11n%40googlegroups.com.
Re: Unable to install or uninstall Tortoise SVN after Drive Crashed
try this: http://support.microsoft.com/mats/program_install_and_uninstall -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/4fb988b3-7568-49ae-a105-b740b8462bd5n%40googlegroups.com.
Re: Win11 .dlls non-accessible after update
I would bet that the problem is a virus scanner on your end. Those react sometimes rather violently if they discover files with ssl in the name and lock those files to fully scan them. Add your working copies to the virus scanners exclusion list. Otherwise you'll get more such problems. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/ea4806a0-fa04-40e9-b45e-cdd02a3ba4d3n%40googlegroups.com.
Re: 1.12.2 running on Server 2019 with client certificate authentication not working
On Saturday, March 11, 2023 at 3:00:59 PM UTC+1 a.hest...@gmail.com wrote: I digged a bit deeper on this and here is my analysis result and suggestion: 1. I understand SVN & TortoiseSVN work with P12-formatted certificates only. 2. This format is supported by OpenSSL only, if the "legacy" provider is activated. Easy to proof that reproducible on Linux: Install openssl 3.x and without activating the legacy-provider it won't support P12 (aka PFX) certificates. The "legacy" profider needs to be activated in openssl.cfn. not quite correct. p12 is supported, but old/deprecated/insecure ciphers are not anymore. So if you created your p12 file with such an old cipher, then it won't work anymore. Also, TSVN is still built with OpenSSL 1.1.1. All you have to do is get a new certificate for your server that uses a recent cipher. And honestly, if you have a certificate on your server that's not supported by TSVN, then you should update it anyway, not just because of TSVN but because the encryption used isn't secure anymore. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/525358b1-990e-476c-ad53-95c09cf6fe10n%40googlegroups.com.
Re: No Cleanup button to be found
that context menu is shown for unversioned folders, not folders recognized as svn working copies. So that's why the cleanup command is not shown. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/66f979df-2a0e-4b7d-a4b0-0b0375a67683n%40googlegroups.com.
Re: [Feature request with patch] Copy revision numbers as hyperlinks
Thanks! That's actually a good idea! Committed in r29529, with minor changes. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/f55883ce-1abf-4ec5-a735-b7a151eef6a6n%40googlegroups.com.
Re: [BUG] "Show All"/"Show Range" button inverted
Thanks! committed in r29528 -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/67c0a478-42be-40c4-9343-9aa0ee9ebb64n%40googlegroups.com.
Re: [Feature request with patch]: Show log at revision
committed your patch in r29527 but I changed it slightly so that your new menu entry only shows when shift is pressed (extended menu). The reason that showing an old revision range from an existing log dialog is very slow is the peg revision. You see, the log dialog is usually started to show the log from HEAD. So the HEAD revision is used as the peg revision to then show the revision range you specify. Setting the peg revision to HEAD is necessary in case the branch you're showing the log for was renamed or was created after the revision range you specify. And the context menu 'verb' string is used when using the ShellExecute or ShellExecuteEx API: https://learn.microsoft.com/en-us/windows/win32/api/shellapi/nf-shellapi-shellexecutea There you can specify a path and a verb. It's not really necessary to implement those, but it doesn't hurt. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/1b2dda9a-8398-4d8b-a2e8-87b389231696n%40googlegroups.com.
Re: [Feature request with patch] Add hotkeys for Copy Revisions
committed your patch in r29526 -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/8f982256-9a37-4097-88a4-02ab4933b076n%40googlegroups.com.
Re: Long time bug: after committing the TortoiseSVN hides behind explorer.
I don't think this is a bug in TSVN. I have a strong suspicion that you have some tool installed that causes this behavior. You see, ever since Win7 Windows decides itself which window gets to be in front. That was because many apps started to misbehave and forced their window to the foreground, annoying users who were typing in another window. That's why a process can not bring it's own window to the front anymore. See the remarks section for the SetForegroundWindow API: https://learn.microsoft.com/en-us/windows/win32/api/winuser/nf-winuser-setforegroundwindow Also, I've never seen this kind of behavior myself, and I'm using TSVN on multiple machines with three different OS versions (Win7, ok that one will be replaced soon, Win10 and Win11). -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/1e7a15e4-cbca-4a25-bdbb-df11a2445a05n%40googlegroups.com.
Re: [Feature request with patch]: Show log at revision
On Monday, February 13, 2023 at 8:35:41 PM UTC+1 Dave Lawrence wrote: Dang, after decades of using Tortoise I, just realized there are extra menu items when you hold down shift! How about we add this new command right after Show Log with the ITEMIS_EXTENDED flag? That would make it more discoverable than just changing the behavior of the existing Show Log command. I think I'd prefer keeping it hidden by default anyway now that I know that's an option. the trick with the shift key is documented: https://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug.html#tsvn-dug-general-menu Also this is really an explorer feature, so other shell extensions use this as well. You might for example notice that if you right-click on a folder while holding down shift, you will also see a context menu entry for "open console here" (or something with that meaning, don't know the exact text in the English version). But even if we add another context menu entry for the extended menu, I still don't like the idea of adding yet another entry to the already crowded menu. I mean this use case is very rare. does the powershell script not work for you? -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/84916517-d47c-4d16-b517-577e9d788771n%40googlegroups.com.
Re: Feature sign commits ?
unlike in Git, signing commits is has no use for SVN. In Git, you can rewrite the history using doing a forced push. In SVN, revisions are immutable. You *can* change revisions in SVN if you have root access on the server and access to the filesystem there. And you have to be able to take the repo offline while you want to change the existing revisions. But if you have that kind of access, signing a commit won't help anyway... -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/593498d0-036f-433d-9b04-7dfd2b2863d6n%40googlegroups.com.
Re: [Feature request with patch] Add hotkeys for Copy Revisions
Thanks for your patch, but it doesn't compile. I guess because the resource.h file is in utf-16 and therefore not included in the patch file. please check r29525, maybe that's what you're looking for? -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to tortoisesvn+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/81cfbcf5-8c38-48af-8855-7db445e8dddbn%40googlegroups.com.
