Conrad T. Pino [EMAIL PROTECTED] wrote:
The CVS project compiles the Windows CVS binary with Microsoft Visual
Studio 6.0 which doesn't have a fchdir implementation which is used
in save-cwd.c module. The comments say:
Some systems lack fchdir altogether: e.g., OS/2, pre-2001 Cygwin,
Jim Meyering wrote:
Is it an option to use a more modern/POSIX-compliant development
environment on Windows? I know that Cygwin now has fchdir
and it looks
like MKS has support for it, too.
If you opt to continue using Visual Studio 6 in
spite of this, it must have some important
Hi:
Using CVS 1.11.17 running as a pserver on UNIX AIX 5.1 we had a core dump of
the CVS server when accessing with wincvs 1.3. Here is a core dump showing the
routine causing the segmentation fault. We have not had a problem with the
most recent version of tortoise but wincvs seems to be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim.Hyslop wrote:
| Jim Meyering wrote:
|
| Is it an option to use a more modern/POSIX-compliant development
| environment on Windows? I know that Cygwin now has fchdir and it
| looks like MKS has support for it, too.
|
|
| If you opt to continue
On Tuesday 08 March 2005 16:37, Derek Price wrote:
Jim.Hyslop wrote:
| Jim Meyering wrote:
| Is it an option to use a more modern/POSIX-compliant development
| environment on Windows? I know that Cygwin now has fchdir and it
| looks like MKS has support for it, too.
|
|
| If you opt to
Derek Price [EMAIL PROTECTED] wrote:
I'm afraid I have to agree with Jim Hyslop. Whatever Microsoft's
flaws, I still believe that some of our mutual user base is at least
relatively innocent and should still be catered to.
This is not about Microsoft per se, but simply about
the lack of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jim Meyering wrote:
| Derek Price [EMAIL PROTECTED] wrote:
|
| I'm afraid I have to agree with Jim Hyslop. Whatever Microsoft's
| flaws, I still believe that some of our mutual user base is at
| least relatively innocent and should still be catered
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Larry Jones wrote:
| Andrew Morton writes:
|
| On a dual 2.7GHz power4, the cvs client has racked up an hour of
| CPU time so far. There's something in there which is quadratic
| (or worse) in the number of files in a directory.
|
|
| Yes, the fix for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Derek,
From: Derek Price [mailto:[EMAIL PROTECTED]
I've attached the diff. Conrad or somebody, would you mind verifying
that after applying this patch (on WOE32, only the two named files will
be relevant)...
Please define the phrase two
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The build process on Solaris 8 Intel Edition seems
to generate lib/stdint.h as an intermediate build
product.
Is there any objection to adding stdint.h to the
lib/.cvsignore file?
-BEGIN PGP SIGNATURE-
Version: PGP 7.0.4
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Conrad T. Pino wrote:
| The build process on Solaris 8 Intel Edition seems to generate
| lib/stdint.h as an intermediate build product.
|
| Is there any objection to adding stdint.h to the lib/.cvsignore
| file?
None whatsoever. :)
Regards,
Derek
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Any further thoughts on this patch?
| 2005-03-04 Derek R. Price [EMAIL PROTECTED]
|
| * lib/wait-process.h (wait_subprocess): Accept a new exitsignal
| argument. * lib/wait-process.c (wait_subprocess): Always set
| *exitsignal to 0 when present and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Conrad T. Pino wrote:
|
| Hi Derek,
|
| From: Derek Price [mailto:[EMAIL PROTECTED]
|
| I've attached the diff. Conrad or somebody, would you mind
| verifying that after applying this patch (on WOE32, only the two
| named files will be relevant)...
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Derek,
From: Derek Price [mailto:[EMAIL PROTECTED]
The two files are listed in the subject line. :)
Oops, I need another cup of coffee!! :)
First off, the problem cited in your output is not caused by the patch
I just sent, but I'll
Derek Price wrote:
Actually moving the code would be complicated and not symetrical. I
dislike having a process responsible for disposing of temporary data it
did not create.
In the CVS client/server architecture, there are two servers. The first
authenticates the client and interprets the
Here is a more detailed description of the tag-extensions:
Terminologie:
Following the mainline (backwards):
Starting from a specific rev. number X on the trunk or a branch, the line is
followed backwards up to the first revision Z on the trunk. It doesn't matter
if there are dead or missing
16 matches
Mail list logo
