> On Sep 23, 2019, at 8:35 AM, Stefan Sperling wrote:
>
>> On Mon, Sep 23, 2019 at 01:53:58PM +0200, Branko Čibej wrote:
>>> On 23.09.2019 13:20, Kumar, Raushan wrote:
>>>
>>> Hi Team,
>>>
>>>
>>> I created a perforce dump using p42svn perl script, it created
>>> successfully as showing in
On Mon, 23 Sep 2019 14:58:58 -0400, Mark Phippard
wrote:
>> D:\Engineering\Projects\Subversion\HW\TcpCommTest>svn status
>> ! TCPCommTest.exe
>> ? TcpCommTest.exe
>>
>> This was an unexpected response I have not seen before...
>>
>> The TcpComm.exe was about 19 Mb in size before the s
On Mon, Sep 23, 2019 at 2:25 PM Bo Berglund wrote:
> I just checked out a project from SVN (1.9.7) and it took a lot
> of time to get the executable.
> This means that the exe file contains debugging symbols so I used
> the command strip -s to clean the exe file. Sdomehow I had forgotten
> this w
I just checked out a project from SVN (1.9.7) and it took a lot
of time to get the executable.
This means that the exe file contains debugging symbols so I used
the command strip -s to clean the exe file. Sdomehow I had forgotten
this when it was committed 2 years ago.
The strip worked fine and
On Mon, Sep 23, 2019 at 01:53:58PM +0200, Branko Čibej wrote:
> On 23.09.2019 13:20, Kumar, Raushan wrote:
> >
> > Hi Team,
> >
> >
> > I created a perforce dump using p42svn perl script, it created
> > successfully as showing in below screen.
> >
> > it is created successfully but while importing
On 23.09.2019 13:20, Kumar, Raushan wrote:
>
> Hi Team,
>
>
> I created a perforce dump using p42svn perl script, it created
> successfully as showing in below screen.
>
> it is created successfully but while importing it on svn server
> showing checksum mismatch error, as showing in below screen.
