[I sent a message with similar content earlier today, but have not gotten it
back through the list, so I'm repeating.]
On Wed, Jun 14, 2000 at 03:56:06PM -0500, Robert Bresner wrote:
> In my leetle mind, I imagine some Perl script running at night, which would
> (ugh) file by file pull down the l
On Wed, Jun 14, 2000 at 03:56:06PM -0500, Robert Bresner wrote:
> [mixed CVS/PVCS project (one team using each, with nightly
> merges]
>
> In my leetle mind, I imagine some Perl script running at night, which would
> (ugh) file by file pull down the latest PVCS and CVS versions, merge them,
> (t
> PVCS (apparently?) provides security on a file by file basis.
> Or, at least an 'object by object' basis (or, in my CVS world, a
> "directory by directory" or, "module by module" basis )
> on a user by user basis. Where
> user A can check
> out a directory, but not check in changes. User B c
On Wed, Jun 14, 2000 at 03:56:06PM -0500, Robert Bresner wrote:
>
>
> Donald Sharp wrote:
> > Bad Mojo. Don't go there. Does PVCS treat branches
> > and files the same as cvs?
>
> Honestly don't know. PVCS, being a very expensive product,
> is unavailable to me, and the customer using it ha
Donald Sharp wrote:
> Bad Mojo. Don't go there. Does PVCS treat branches
> and files the same as cvs?
Honestly don't know. PVCS, being a very expensive product,
is unavailable to me, and the customer using it has a similar
amount of CVS knowledge that I have of PVCS.
Their mindset of versi
On Wed, Jun 14, 2000 at 12:22:16PM -0500, Robert Bresner wrote:
> Howdy,
>
> The short version is that I'm looking for a way to
> import a CVS repository into PVCS, and, (get this)
> to have one team of developers use CVS while another
> team is using PVCS and, overnight, the two repositories
