What happens when you try to do it?  Is it a problem with the shell?  Have you
tried CygWin's bash?

Noel




[EMAIL PROTECTED] on 05/30/2000 04:56:45 PM

Please respond to [EMAIL PROTECTED]

To:   [EMAIL PROTECTED]
cc:   [EMAIL PROTECTED]
Subject:  RE: Synchronization - Production.




CVS on NT doesn't seem to understand DOS commands. I can't Put DOS commands
in the loginfo file. I can neither call a batch file with DOS commands.
So, what can I put in the loginfo file? (to work on NT).
(I think about mounting an NT partition on a Linux with Samba).
I'd like to avoid that solution.

This is wath I want to do.
PC ----> CVS on NT --------> Web Site on IIS.

As soon as I commit a file, I want the Web Site up to date.

I know how to do it on Unix(or Linux), but on NT it doesn't work the same.
As I say before, I can't put DOS commands in the loginfo.

If somebody did it or have a guess about it, help me.

Thanks for your help

Daniel Barsalou
[EMAIL PROTECTED]


-----Original Message-----
From: Noel L Yap [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 30, 2000 9:56 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Synchronization - Production.


I've only used client CVS on NT.  My guess, though, is that any executable
can
be placed in loginfo so, just have loginfo execute a batch file (or whatever
NT
uses nowadays).

Also, the limititations of your technology shouldn't be an excuse for poor
process.  At the very least, I would have a staging site that gets a
once-over
before being exported to production.

Noel




[EMAIL PROTECTED] on 05/30/2000 05:33:46 AM

To:   [EMAIL PROTECTED]
cc:   [EMAIL PROTECTED]
Subject:  Re: Synchronization - Production.










This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.

Reply via email to