On 4/24/05, A. J. Mechelynck wrote:
> Bill McCarthy wrote:
> > I use CVS on XP Pro and MinGW - a native windows
> > implementation. Nothing needs changing. My make
> > one-line 4nt alias to build Gvim is: [...]
> I meant "change what needs changing" as compared to the procedures
> described in my HowTo page. Using CVS Mikolaj probably wouldn't do any
> patching, and he might even dispense with Cygwin completely if compiling
> with BCC, since IIUC CVS also bypasses the need to use bunzip2 on the
> source distribution. OTOH, since I don't use CVS myself, my HowTo page
> doesn't mention it.
To add to Tony's, there are several tools under Windows that shield
you from CVS's command line. I've read good things about TortoiseCVS
wich integrates with the explorer shell and becomes a contextual menu
you use on folders and files. And for the more conservative there is
WinCVS, which is a stand-alone application. I haven't used either tool
in earnest. But I've used tkCVS with cygwin, which gives you nice
graphical representations of a CVS repository change history.
BTW, both tools mentioned above do not use CVS. Rather use CVSNT, a
fork that not only is fully compatible with CVS but is a fully working
win32 server and supports advanced branching and merging not available
by the original CVS code. The original CVS Win32 port is client only.