Dear Subversion enthousiasts,
apart from some issues around the use of changesets, or the use of patches, I
couldn't find anything on the subject of using the 4eyes priciple with
subversion.
I would hate to go through the process of stopping to work with subversion and
install something new
On Fri, Dec 8, 2017 at 10:58 AM, Hans HESPEN wrote:
> Dear Subversion enthousiasts,
>
> apart from some issues around the use of changesets, or the use of patches,
> I couldn't find anything on the subject of using the 4eyes priciple with
> subversion.
>
> I would hate to go through the process of
On Thu, 07 Dec 2017 21:44:08 +0100, Bo Berglund
wrote:
>Problem:
>I have taken one of our CVS repositories, which contains just 16
>projects, as a test case for the full conversion to come later.
>I used the options file approach so that I could use the automatic
>listing of these projects.
>What
I am very confused about the vast difference between the cvs2svn
command line options and what is visible in he example options file...
When I run into trouble with a conversion some suggestions are printed
on the console but they all target adding something to the command
line, which I cannot do
On 08.12.2017 12:32, Bo Berglund wrote:
> I am very confused about the vast difference between the cvs2svn
> command line options and what is visible in he example options file...
>
> When I run into trouble with a conversion some suggestions are printed
> on the console but they all target adding
On Fri, 8 Dec 2017 12:41:48 +0100, Branko ?ibej
wrote:
>On 08.12.2017 12:32, Bo Berglund wrote:
>> And the options file syntax seems to be completely different from the
>> command line...
>>
>> Please advice, I have read the documentation but it fails to mention
>> this at least where I have read
I think Hans means code review prior to the commit landing in branch that
other people are continually doing 'svn up' from.
If so, Rietveld, Gerrit specifically enable code review before the commit
lands. Commercial vendors such as RhodeCode an Assembla have code-review
capabilities in their large
Dear Paul & Johan,
thank you for your reply. Indeed, 4 eyes principle is like Paul says.
The 4 eyes-principle is known for important decisions. Some decisions can't be
made by a single person, and need to be made by two persons, for instance a CEO
and the CFO. Launching a nuclear missile need
On Fri, Dec 08, 2017 at 03:13:41PM +, Hans HESPEN wrote:
> Anyway, Paul has put me on the line of code review tools, post and
> pre-commit. Tools like RhodeCode, Crucible, Rietveld, Collaborator. This is
> actually a bit too much for what I was looking for, but this might be a very
> good alter
On Fri, 08 Dec 2017 12:24:19 +0100, Bo Berglund
wrote:
>What am I missing? It seems like the symbol handling defined in the
>options file is not used
I ended up putting the following into the options file where the
sub-projects are defined:
import os
cvs_repo_main_dir = '/home/bosse/CVSREPO
On Fri, Dec 8, 2017 at 10:13 AM, Hans HESPEN
wrote:
> Dear Paul & Johan,
>
>
> thank you for your reply. Indeed, 4 eyes principle is like Paul says.
>
>
> The 4 eyes-principle is known for important decisions. Some decisions
> can't be made by a single person, and need to be made by two persons,
On Fri, Dec 8, 2017 at 6:41 AM, Branko Čibej wrote:
> On 08.12.2017 12:32, Bo Berglund wrote:
>> I am very confused about the vast difference between the cvs2svn
>> command line options and what is visible in he example options file...
>>
>> When I run into trouble with a conversion some suggestio
Hi,
during the Hackathon, jamessan made me aware of a webinar Assembla put
on their webpage. Finally I got some time this week watching it
completely. Talking about it on IRC, jcorvel suggested that others on
the users mailing list here might be interested in that one too. So if
those who jcorval
13 matches
Mail list logo
