Here's a patch that should restore the ability of save-cwd to
work on systems without the fchdir function.
Would you please see if this is sufficient?
If so, I'll check it in to gnulib (with an AC_CHECK_FUNCS(fchdir)
in save-cwd.m4).
Index: save-cwd.c
Hi,
Could anyone shed some light on this peculiarity of the diff3 utility?
Here’s the example OLDFile is as below,
#ENGLISH Resource File
#DoNotTranslate
L6_WINDOWS = OK|O
# fail to enable path.
Some times when I do a CVS commit, text like the following is appended
to the bottom of the file that I have committed:
**
date: Friday, February 18, 19105 @ 14:44
author: username
Update of /data/implementation/cvs/operational/bin
In directory
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bruno Haible wrote:
| Thanks for explaining. Your objective is clear now.
|
| But how would you want this to work on Woe32? I assume that you
| would want this debugging feature also on Windows. How do you
| implement it there?
Actually, the CVS server
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Jim,
From: Jim Meyering [mailto:[EMAIL PROTECTED]
This is not about Microsoft per se, but simply about
the lack of fchdir (or POSIX support in general) in WOE.
I agree let's not enumerate Microsoft's flaws as we would never
finish. :)
I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Jim,
From: Jim Meyering [mailto:[EMAIL PROTECTED]
Here's a patch that should restore the ability of save-cwd to
work on systems without the fchdir function.
Would you please see if this is sufficient?
If so, I'll check it in to gnulib
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Frank Hemer wrote:
| Here is a more detailed description of the tag-extensions:
Mostly this sounds great, with the few questions/exceptions that I
have noted.
Could you write the final version up as a patch to doc/cvs.texinfo?
| '.origin': Will always
Romeo Gourgue wrote two variations on the following:
Some times when I do a CVS commit, text like the following is appended
to the bottom of the file that I have committed:
**
date: Friday, February 18, 19105 @ 14:44
author: username
Update of
On Wednesday 09 March 2005 15:50, Derek Price wrote:
Frank Hemer wrote:
| Here is a more detailed description of the tag-extensions:
Mostly this sounds great, with the few questions/exceptions that I
have noted.
Could you write the final version up as a patch to doc/cvs.texinfo?
I
Hi,
the 1.12.x series contains the http tunnel web proxy patch. This patch
originaly allowed to specify the proxy and proxyport using environment
variables (PSERVER_PROXY) in the form of 'my.proxy.server[:PORT]', in
addition to specifying it in the CVSROOT. This has the advantage of not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Derek,
I'm slow to understand the goal. I'm coming to the conclusion
what you're trying is eliminate the difference between:
*** config.h.in, generated by mkconfig:
as opposed to:
*** config.h.in, generated by mkconfig.pl:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Frank Hemer wrote:
| On Wednesday 09 March 2005 15:50, Derek Price wrote:
|
| Frank Hemer wrote: | Here is a more detailed description of the
| tag-extensions:
|
| Mostly this sounds great, with the few questions/exceptions that
| I have noted.
|
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Conrad T. Pino wrote:
| Previously I wasn't aware of the existence of the intermediates on
| UNIX and of course they don't exist on Windows. The commands I ran
| on both Windows and UNIX are:
|
| cd ccvs perl windows-NT/fix-msvc-mak.pl cd windows-NT
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Derek Price [EMAIL PROTECTED] writes:
In the case where the information came out of the directory CVS/Tag
file, it becomes available in vers-nonbranch, but not otherwise.
In other cases, the RCS file gets parsed anyhow, but only on the
server.
| | '.origin': Will always resolve to the very first revision. If a
| |
| | file has been added on a branch, .origin will resolve to the
|
| first | revision on that branch, otherwise it will follow the
| mainline. | | '.root': Will resolv to the predecessor of the
| first revision on |
On Wednesday 09 March 2005 21:08, Mark D. Baushke wrote:
Derek Price [EMAIL PROTECTED] writes:
In the case where the information came out of the directory CVS/Tag
file, it becomes available in vers-nonbranch, but not otherwise.
In other cases, the RCS file gets parsed anyhow, but only on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Frank Hemer wrote:
| a revision on BRANCH's parent. This makes sense when speaking
| about individual files, but use of .origin with multiple files
| probably deserves some sort of warning to the user that what they
| asked for may not make sense.
|
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Derek Price [EMAIL PROTECTED] writes:
Frank Hemer wrote:
| a revision on BRANCH's parent. This makes sense when speaking
| about individual files, but use of .origin with multiple files
| probably deserves some sort of warning to the user that
Conrad T. Pino [EMAIL PROTECTED] wrote:
...
Would you please see if this is sufficient?
If so, I'll check it in to gnulib (with an AC_CHECK_FUNCS(fchdir)
in save-cwd.m4).
The patch as submitted does not compile. This line fails:
return fchdir (cwd-desc);
The patch at message end does
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Jim,
From: Jim Meyering [mailto:[EMAIL PROTECTED]
Conrad T. Pino [EMAIL PROTECTED] wrote:
...
Would you please see if this is sufficient?
If so, I'll check it in to gnulib (with an AC_CHECK_FUNCS(fchdir)
in save-cwd.m4).
The patch
20 matches
Mail list logo
