Site and obsolete Svn info

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Site and obsolete Svn info

Jacques Le Roux
Administrator
Hi,

As I wrote in OFBIZ-11269 at https://s.apache.org/pf2ty, please consider:

We should change in the  "Committer Access" section of source-repositories.tpl.php

When you first connect you will be prompted to accept the SSL certificate. Verify the certificate is for svn.apache.org. After verification, select
option 'P' to permanently add to your SVN configuration.
Subversion can handle keyword expansion, eol conversion as well as many other features. These features are configured at the server level (actually
only in the OFBiz repository branch), so you don't have to worry about them

I propose

When you first connect you will be prompted to accept the SSL certificate. Verify the certificate.
Git handles keyword expansion, EOL conversion as well as many other features. These features are configured at the server level, so you don't have to
worry about them

But I'm unsure if we should change
after verification, select option 'P' to permanently add to your SVN configuration.
or simply remove it...

What do you think?

Jacques

Reply | Threaded
Open this post in threaded view
|

Re: Site and obsolete Svn info

Jacques Le Roux
Administrator
Done by removing the last references to Svn

Le 04/05/2020 à 12:27, Jacques Le Roux a écrit :

> Hi,
>
> As I wrote in OFBIZ-11269 at https://s.apache.org/pf2ty, please consider:
>
> We should change in the  "Committer Access" section of source-repositories.tpl.php
>
> When you first connect you will be prompted to accept the SSL certificate. Verify the certificate is for svn.apache.org. After verification, select
> option 'P' to permanently add to your SVN configuration.
> Subversion can handle keyword expansion, eol conversion as well as many other features. These features are configured at the server level (actually
> only in the OFBiz repository branch), so you don't have to worry about them
>
> I propose
>
> When you first connect you will be prompted to accept the SSL certificate. Verify the certificate.
> Git handles keyword expansion, EOL conversion as well as many other features. These features are configured at the server level, so you don't have
> to worry about them
>
> But I'm unsure if we should change
> after verification, select option 'P' to permanently add to your SVN configuration.
> or simply remove it...
>
> What do you think?
>
> Jacques
>