Chethan Pandarinath <cpandar@...> Sat, 27 Oct 2001 12:57:43
> I would like to use tramp now, and I was wondering what my best
> option is. Is there a pre-bug version of tramp I can check out from
> CVS (even if it means using the old filename syntax)? I can use su,
> sm, or scp methods, but they all return the 'No files match' error
> with the current version of tramp.
I've noticed some traffic about problems since the filename-syntax
change. I don't notice a solution--am I missing something?
If no solution: how does this sound as a workaround: releasing an
Minimally, I've got a tarball from the spring (featuring tramp.el
version 2.13) that "I know works": at least, having unpacked it from
my netware filespace and installed it on a linux box, I can do
from the latter box. (I've separately sent this to my fellow NCSUer,
along with some notes from my epic struggle with our Unity environment
So I was thinking, why not create a tramp-oldstyle version? If so,
is there a better way to do it than I've indicated above?
This also made me wonder:
> Is there a pre-bug version of tramp I can check out from CVS
can one currently checkout _releases_ via CVS? (Not in the SF sense of
tarballs, but rather the set of files to which an SF release would
unpack.) I know the above tarball has tramp-version 2.13, but, IIRC,
that really only refers to tramp.el. If I didn't have an old "release"
squirreled away, I wouldn't know how to get all the other files
(notably tramp.texi) that "go with" it, other than by inspecting dates
of versions in each ChangeLog. Granted, virtually all of the CVS
activity is done for tramp.el, but you see the point ... or am I