[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: kcvs
From:       Frugal <frugal () fysh ! org>
Date:       1998-06-17 8:00:24
[Download RAW message or body]

Stefan Marx wrote:
> 
> Kalle Dalheimer wrote:
> >
> > I'd go for using cvs. You can only introduce bugs if you want to
> > implement the client side yourself, but have nothing much to
> > gain. Have a look at the class KProcess for easy access to external
> > processes.
>
> I fully agree with Kalle in this point. The cvs-command-line tools are
> stable and will trace their output to the standard-input, output chanels
> in a good looking format IMHO, I have done some parseing on this outputs
> while coding some experimental java-clients for cvs (Just before I get
> tkcvs or something like that).
> 
> But some other idea, what's about an CVS-Protocol for kfm, as extra-tool
> or while sharing lot's of code with kcvs, So you maybe will be able to
> browse a cvs-server in kfm. I don't know if this will works fine,
> because cvs can cause long delay-times.
> 
> But a kcvs will be very fine, and maybee the KIDE or Kbuilder developers
> are interested in this tool too.

Absoulutly, CVS support is a definite for MAWC. I just havn't figured
out how I was going to implement it in an intuative way.

-- 
Frugal                      + I would be infinitely more comfortable in
                            + your presence if you we treat gravity as
frugal@fysh.org             + a law, rather than one of a number of
frugal@wardrobe.demon.co.uk + suggested options - Neil Gaiman (Sandman)

[prev in list] [next in list] [prev in thread] [next in thread]