* where to get the newest version of pcl-cvs ?
@ 2004-10-13 12:36 Martin Jost
0 siblings, 0 replies; 4+ messages in thread
From: Martin Jost @ 2004-10-13 12:36 UTC (permalink / raw)
Hello,
newer versions of cvs (e.g. 1.12.9) break pcl-cvs (the version coming with emacs 21.2) at least partly.
I tried to get hold of a newer version of pcl-cvs but failed.
- All my old bookmarks are too old or dead
- All the pointers I could find in pcl-cvs or cvs itself were either too old or didn't worked at all.
- cvshome und cvs-bubbles also brought up only too old info (or didn't work like the FAQ-O-Matic)
- The project on sourceforge is simply empty
- Googling didn't bring up a place to download (but many hits on my keywords)
So: Where are the up to date versions of pcl-cvs kept ?
TIA
Martin
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: where to get the newest version of pcl-cvs ?
[not found] <ckj7g3$4n8$1@news.mch.sbs.de>
@ 2004-10-13 16:01 ` Greg A. Woods
2004-10-13 21:24 ` Stefan Monnier
[not found] ` <jwvzn2qfh8z.fsf-monnier+gnu.emacs.help@gnu.org>
2 siblings, 0 replies; 4+ messages in thread
From: Greg A. Woods @ 2004-10-13 16:01 UTC (permalink / raw)
Cc: CVS-II Discussion Mailing List
[ On Wednesday, October 13, 2004 at 14:36:17 (+0200), Martin Jost wrote: ]
> Subject: where to get the newest version of pcl-cvs ?
>
> newer versions of cvs (e.g. 1.12.9) break pcl-cvs (the version coming with emacs 21.2) at least partly.
> I tried to get hold of a newer version of pcl-cvs but failed.
Did you try getting a newer version of Emacs? The latest version of GNU
Emacs is 21.3, available since March 24, 2003, and it still includes
PCL-CVS as part of the base elisp applications.
I haven't had any trouble with it, but I'm not sure I'm using the latest
versions of CVS. :-)
--
Greg A. Woods
+1 416 218-0098 VE3TCP RoboHack <woods@robohack.ca>
Planix, Inc. <woods@planix.com> Secrets of the Weird <woods@weird.com>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: where to get the newest version of pcl-cvs ?
[not found] <ckj7g3$4n8$1@news.mch.sbs.de>
2004-10-13 16:01 ` where to get the newest version of pcl-cvs ? Greg A. Woods
@ 2004-10-13 21:24 ` Stefan Monnier
[not found] ` <jwvzn2qfh8z.fsf-monnier+gnu.emacs.help@gnu.org>
2 siblings, 0 replies; 4+ messages in thread
From: Stefan Monnier @ 2004-10-13 21:24 UTC (permalink / raw)
> So: Where are the up to date versions of pcl-cvs kept ?
In Emacs's CVS repository.
As for the 1.12.9 problem, it's not really fixed there, because the problem
is that the commit messages have become ambiguous and there's nothing
PCL-CVS can do about it, really. Hopefully it'll get fixed in 1.12.10.
Stefan
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: where to get the newest version of pcl-cvs ?
[not found] ` <jwvzn2qfh8z.fsf-monnier+gnu.emacs.help@gnu.org>
@ 2004-10-14 11:25 ` Martin Jost
0 siblings, 0 replies; 4+ messages in thread
From: Martin Jost @ 2004-10-14 11:25 UTC (permalink / raw)
Hello,
here, just some notes on the answers I got (all public as answers into news)
"Stefan Monnier" <monnier@iro.umontreal.ca> schrieb im Newsbeitrag news:jwvzn2qfh8z.fsf-monnier+gnu.emacs.help@gnu.org...
> > So: Where are the up to date versions of pcl-cvs kept ?
>
> In Emacs's CVS repository.
> As for the 1.12.9 problem, it's not really fixed there, because the problem
> is that the commit messages have become ambiguous and there's nothing
> PCL-CVS can do about it, really. Hopefully it'll get fixed in 1.12.10.
Thanks ! (Actually twice !)
So now I know where to look for the bleeding edge and I also know that it will just now _not_ fix my problem.
And: yes I've even found a thread discussing this problem regarding cvs. But I've assumed, that it might be already fixed (I didn't find a cvs version number mentioned in the part of the thread I saw)
"Greg A. Woods" <woods@weird.com> schrieb im Newsbeitrag news:mailman.3047.1097683782.2017.info-cvs@gnu.org...
> Did you try getting a newer version of Emacs? The latest version of GNU
> Emacs is 21.3, available since March 24, 2003, and it still includes
> PCL-CVS as part of the base elisp applications.
I switched back from 21.3 to 21.2 because I got random crashes of 21.3 (on HPUX 10.20) with emacs dying with a SIGALARM. But I never was able to reproduce the problem, so a bug report seemed rather useless.
> I haven't had any trouble with it, but I'm not sure I'm using the latest versions of CVS. :-)
I tried 1.12.9 out of curiosity. This one has a new format for the start of the hook-scripts. So this was problem 1 to fix.
Afterwards pcl-cvs got problems. But now I've already invested (some) time and wanted to solve this.
Unfortunately this won't work at the moment, so I went back to 1.11.17.
"Mark D. Baushke" <mdb@cvshome.org> schrieb im Newsbeitrag news:mailman.3099.1097706102.2017.info-cvs@gnu.org...
> Stefan Monnier <monnier@iro.umontreal.ca> writes:
>
> > As for the 1.12.9 problem, it's not really fixed there, because the problem
> > is that the commit messages have become ambiguous and there's nothing
> > PCL-CVS can do about it, really. Hopefully it'll get fixed in 1.12.10.
>
> cvs 1.12.10 will have the relative pathname on the line that lists the
>
> /full/repository/cvsroot/ path/to/the/file,v <-- to/the/file
> new revision: 3.1.2.1; previous revision: 3.1
>
> instead of the cvs 1.11.x behavior of
[...]
> Maybe if we all ask nicely Stefan can make a new release of pcl-cvs
> available that will work with cvs 1.12.10...
I'm looking forward to the new version of cvs and a new pcl-cvs matching it !
Thanks a lot to everybody who answered
Martin
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2004-10-14 11:25 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <ckj7g3$4n8$1@news.mch.sbs.de>
2004-10-13 16:01 ` where to get the newest version of pcl-cvs ? Greg A. Woods
2004-10-13 21:24 ` Stefan Monnier
[not found] ` <jwvzn2qfh8z.fsf-monnier+gnu.emacs.help@gnu.org>
2004-10-14 11:25 ` Martin Jost
2004-10-13 12:36 Martin Jost
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).