[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: How to get "edit -c" working
RE: How to get "edit -c" working
Fri, 2 Mar 2001 10:54:59 -0800
> address@hidden on 2001.02.28 12:30:31
> >Some things can't be easily versioned under CVS. For example, PL/SQL or
> >other code that lives in the database. Since it's a shared
> resource, we need
> >to do exclusive locking to version it.
> Is there a way to export/import these files as text? If so, you
> can go that
That what we've done (exported the files as text), and then as part of the
checkin process, the DB guys are supposed to commit the change and unlock
the file. Could you tell me more about what you're thinking about here as an
Wait, let me back up. Here's a better explanation of why I think this part
The DB developers have fancy tools to allow them to edit, run, and debug
their code directly in the (single, shared) database. But no tools to keep
versions of the code. They need to keep using those fancy tools.
But when one person is fancily editing the code directly in the DB, we want
to have a portion of the development process inform others that they're not
allowed to edit that piece of code. I had been thinking, export all the DB
code as text, and use exclusive locking.
We're supposed to be using CVS everywhere, not an amalgam of tools, so I
really want to get CVS locking working. But I'm open to another suggestion
if I've missed something. I can't think of how concurrent development would
work with a shared database.
So it sounds like I need to dowload all the patches, apply them, build new
UNIX and Windows executables with the patches, patch our WinCVS installation
with the new binary, and update everyone's installation. Gaack :)
Has anyone pre-built the windows cvs.exe with Noel's patches?
> >So the recommend workaround is to use Noel Yap's "cvs edit -c" patch (hi
> >Noel!) against CVS 1.10.8.
> >I took a look on Sourceforge and there are just zillions of patches to
> >download. Which ones are the ones I need?
> I apologize for the format of these patches. I should've
> submitted one patch
> per feature/bug fix, but instead, I submitted incremental
> patches. Since they
> are incremental, you'll have to install each patch up to and
> including the last
> one you need.
> >Also, and very importantly, is this a server-only patch, or will
> I have to
> >patch all the clients as well?
> The patch are both server and client side. New options have to
> be since the
> client will need to be able to specify the option, and the server
> will need to
> understand it.
> >thanks *so much*,
> >Chris Chambers
> I apologize again for the messiness. I know I keep saying this,
> but if I find
> some time, I'll clean up the patches.
> 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 Chase & Co., its
> subsidiaries and affiliates.
> Info-cvs mailing list