Re: cvs-1.10 includes
"Jerzy Kaczorowski" <[email protected]> Sat, 1 Jan 2005 00:45:17 -0000
| Newsgroups | gmane.comp.version-control.cvs.gui.devel |
|---|---|
| Message-ID | <[email protected]> |
>What is the current thinking on removing cvs-1.10 entirely?
WinCvs is not using that for something like two years now. Perhaps we ought
to get rid of it since gCvs can work with cvsnt and it seems like MacCvs can
use it as well.
Jens, can MacCvs use cvsnt or does it still need cvs from cvs-1.10 folder?
Best Regards,
Jerzy
----- Original Message -----
From: Guy Rouillier
To: CvsGui Dev
Sent: Thursday, December 30, 2004 22:56
Subject: [cvsgui-dev] cvs-1.10 includes
Four files have >include "../lib/getline.h"<:
common/CommitDlg.cpp
common/CvsEntries.cpp
common/CvsIgnore.cpp
also has >#include "../lib/fnmatch.h"<
common/LogParse.cpp
I'm not seeing how these includes can be of assistance on any platform,
since there is no directory ../lib. These two includes are actually in
cvs-1.10/lib. Jens, perhaps on Mac a symlink is created?
At any rate, for gCvs on Linux these includes are not resolved and are
not needed, since the required functions are prototyped in
/usr/include/stdio.h and /usr/include/fnmatch.h. Can someone identify
if they are used on other platforms?
What is the current thinking on removing cvs-1.10 entirely? cvsnt is a
preferable option at this point, and there are a lot of files in that
directory, which greatly slows down checkout and uses up disk space.
--
Guy Rouillier
------------------------ Yahoo! Groups Sponsor --------------------~-->
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/NhFolB/TM
--------------------------------------------------------------------~->
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/cvsgui-dev/
<*> To unsubscribe from this group, send an email to:
[email protected]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/