Ok I see changes are not simple and it could be a bigger change, maybe
breaking (relaxing) some current lock rules. But mind that even the
current implementation has flaws - SVN-2507. So, my approach is to
prefer simplicity and usability over holes-free implementation. From
my point of view, it's i
On 3. 6. 25 17:26, Ondra Medek wrote:
Remarks to Andreas reply. First, I would like to quote Stefan Küng's
comment from SVN-2507: "First, remember that locking is often done by
non-technical people (e.g., designers working on images, non-devs
working on word docs, ...) so they're happy if they ca
Remarks to Andreas reply. First, I would like to quote Stefan Küng's
comment from SVN-2507: "First, remember that locking is often done by
non-technical people (e.g., designers working on images, non-devs
working on word docs, ...) so they're happy if they can use svn at
all."
- So, the point is n
On 2025-06-03 10:59, Daniel Sahlberg wrote:
I think the best option would be to teach `svn commit` to SET a lock
after commit (much like it can be told to not RELEASE the lock on an
already committed file). Then your workflow would be:
1. Create a new empty file.
2. Add it.
3. Commit it, with
> and do svn lock newfile, then got error:
> >>>
> >>> svn: E155010: The node '...\newfile' was not found.
> >>>
> >>> When 2 users create and commit `newfile` at the same time, then one of
> >>> them has a tree conflict.
>
#x27; was not found.
>>>
>>> When 2 users create and commit `newfile` at the same time, then one of
>>> them has a tree conflict.
>>> How to use svn lock for a new file? Or is there any other way to
>>> prevent conflicts when 2 users create the same fi
t; prevent conflicts when 2 users create the same file and the same time?
>> See my SO question
>>
>> https://stackoverflow.com/questions/79639066/how-to-lock-or-prevent-conflicts-for-a-new-file-with-svn/79640745
>> and workaround
>> https://stackoverflow.com/questions/796
koverflow.com/questions/79639066/how-to-lock-or-prevent-conflicts-for-a-new-file-with-svn/79640745
> and workaround
> https://stackoverflow.com/questions/79639066/how-to-lock-or-prevent-conflicts-for-a-new-file-with-svn/79640745
>
> If this functionality is missing, then consider it as
same time, then one of
them has a tree conflict.
How to use svn lock for a new file? Or is there any other way to
prevent conflicts when 2 users create the same file and the same time?
See my SO question
https://stackoverflow.com/questions/79639066/how-to-lock-or-prevent-conflicts-for-a-new-fil
