ot;get the default
revision". Does this make sense?
-Rob A
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 11, 2003 3:22 PM
To: Ant Developers List
Subject: RE: enhanced pvcs task for PVCS version 7.5
PVCS task works with version 7.5
". Does this make sense?
-Rob A
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 11, 2003 3:22 PM
To: Ant Developers List
Subject: RE: enhanced pvcs task for PVCS version 7.5
PVCS task works with version 7.5 as is, unless you are pointing to
etwas so erfolgreich wie Dummheit mit guten
Manieren.
Voltaire
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Ant Developers List" <[EMAIL PROTECTED]>
Sent: Tuesday, March 11, 2003 4:28 PM
Subject: RE: enhanced pvcs task for PVCS version 7.5
>
>
> I&#x
.com>cc:
Subject: RE: enhanced pvcs task
for PVCS version 7.5
- VSCM" To: "'Ant Developers
List'" <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]cc:
I'd be interested in it, although I am a firm believer in maintaining
compatibility with old-style get. A question for the Ant Powers That
Be:
What's the recommended way to do this sort of migration? Create a new
task that's similar to the old but includes the enhancements, or add
options to the
PVCS task works with version 7.5 as is, unless you are pointing to a config
file other than the default. The advatantage to using "pcli get" rather than
"get" is that pcli is smart about config files, which has been a problem for
me with the existing PVCS task. I'm a little new to PVCS Version Mana
