Fri, 27 Dec 2024 16:44:05 +0100, /Bo Berglund/:
So I looked in the RedBean "manual" and found this:
$ svnadmin load /var/svn/restored < repos-backup
<<< Started new txn, based on original revision 1
* adding path : test ... done.
* adding path : test/a ... done.
where they place t
Mon, 23 Sep 2024 19:26:04 +0200, /Bo Berglund/:
By using this it did work (all on one line anmd no extra backslash):
svn delete -m "Deleting file xxx"
https://svnserver/svn/repo/tags/nameofproject/filetodelete
In the Windows Command Prompt (cmd) or batch scripts you could use ^
(caret) [1]:
Fri, 2 Feb 2024, /Johan Corveleyn/:
On Fri, Feb 2, 2024 at 10:18 AM Stanimir Stamenkov via users wrote:
* Tree conflicts flagged by svn merge cannot be automatically resolved
yet. This will be addressed in a future release.
If I understand correctly, not much has changed related to
Fri, 2 Feb 2024, /Sands, Daniel N./:
As far as I'm aware this is all client-side behavior - nothing to do with the
server. Resource move/rename
has always been recorded as a _Delete_ of the original path and a _Copy_ (Add)
from the previous path
revision. It could be I'm missing something here
Tue, 30 Jan 2024, /Sands, Daniel N./:
So far I have not found a use case where moved file resolution in 1.8+
works as advertised on 1.7 servers. But more specifically, I have the
following case:
The trunk has a directory,
/foo/bar
In my local branch, I have relocated bar to
/baz/bar
Meanwh
Wed, 1 Nov 2023 20:36:17 +0530, /JITHIN K/:
The Subversion version in my Ubuntu server is 1.13.0-3ubuntu0.2 and when
I check the change log
https://changelogs.ubuntu.com/changelogs/pool/universe/s/subversion/subversion_1.13.0-3ubuntu0.2/changelog
I could see that security update for CVE-2020-17
