Doug,
Doug Robinson wrote:
> To be more precise, you can know who, in the past, has made changes to files
> and
> checked those change into the repository. You cannot know who has made
> changes
> in their working copy and has not yet checked them back into the repository
> (they
> may never
> Andreas:
>
> On Mon, Jun 6, 2016 at 3:50 AM, Andreas Stieger
> wrote:
> > or knowing who is actually working on a file.
>
> Incorrect, this is shown in both TortoiseSVN and svn cli.
>
> To be more precise, you can know who, in the past, has made changes to files
> and
> checked those change
On Mon, Jun 6, 2016 at 3:47 PM, Doug Robinson
wrote:
> Andreas:
>
> On Mon, Jun 6, 2016 at 3:50 AM, Andreas Stieger
> wrote:
>
>> > or knowing who is actually working on a file.
>>
>> Incorrect, this is shown in both TortoiseSVN and svn cli.
>>
>
> To be more precise, you can know who, in the pa
Andreas:
On Mon, Jun 6, 2016 at 3:50 AM, Andreas Stieger
wrote:
> > or knowing who is actually working on a file.
>
> Incorrect, this is shown in both TortoiseSVN and svn cli.
>
To be more precise, you can know who, in the past, has made changes to
files
*and*checked those change into the repos
Hi,
> in Tortoise SVN, there is no method of locking a file until it has been
> changed .
Incorrect. locking, requiring locking and lock communication are supported by
both plain svn and TortoiseSVN.
https://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-dug-locking.html
http://svnbook.red-b
