Arkadiusz Miskiewicz wrote:
> IPv6 support seems quite broken in cvsnt (looking at 2.5.04.3236)
>
> It doesn't support [ipv6]:port notation, binds to ::1 port while it should
> bind to ipv4 address, too (cvslockd as example. Server tries to
> use "localhost" name which resolves only to 127.0.0.1
IPv6 support seems quite broken in cvsnt (looking at 2.5.04.3236)
It doesn't support [ipv6]:port notation, binds to ::1 port while it should
bind to ipv4 address, too (cvslockd as example. Server tries to
use "localhost" name which resolves only to 127.0.0.1 address, tries to
connect to it but
Gerhard wrote:
> Hello,
>
> In the CVSNT manual it says about the update -f option:
>
> "If no matching revision is found, retrieve the most recent revision
> (instead of ignoring the file)."
>
> In the TCVS Update Special dialog, there is a checkbox with a label
> that sounds similar.
>
> Howe
>> We had implemented such this tool some time ago, when we migrated
>> to 2.5.03.
>> You can check this out at
>> http://www.3ia.com.br/cms/index.php/download/37-cvsnt-hit
>
> Interesting piece of code!
> It could simply be made portable across database backends
>> (supported by the ADO system
Hello,
In the CVSNT manual it says about the update -f option:
"If no matching revision is found, retrieve the most recent revision
(instead of ignoring the file)."
In the TCVS Update Special dialog, there is a checkbox with a label
that sounds similar.
However, I think both are wrong. When I u
On Wed, 5 Nov 2008 11:02:06 -0200, "Ronaldo Capaverde"
<[EMAIL PROTECTED]> wrote:
>We had implemented such this tool some time ago, when we migrated to 2.5.03.
>You can check this out at
>http://www.3ia.com.br/cms/index.php/download/37-cvsnt-hit
Interesting piece of code!
It could simply be made