New binutils available from cvs
Quoted 6 lines · Alan Modra
Quoted 3 lines · Philipp Rumpf
Any reason for renaming cvs modules all the time instead of staying with one name and perhaps not pissing off people with slow, expensive connections ?
Mainly so people can still easily use the old binutils. .diff.gz came to
[...]
That's what tags and branches are for! *Please* use CVS the way it was meant to be used, don't use it like some old SCCS system!
It's now close to impossible to track these things. cvs co -c doesn't show the modules either, without keeping *very* close tracking of the mailing list we won't even know what we should/can use.
Quoted 1 line
1.8M anyway. I can put the diff somewhere you can get it, if you like.
Sigh. What *for*? See above, that's why CVS has branches and tags which makes it easy for users to:
a) See what's in there (cvs status -v)
b) Switch between versions with ease and with minimal bandwidth
c) Keep several versions locally (copy a tree and switch to other branch or rev.)
-Tor
Quoted 2 lines · Tor Arntsen
That's what tags and branches are for! *Please* use CVS the way it was meant to be used, don't use it like some old SCCS system!
the trouble is that none of us are sufficiently skilled with CVS to cope with the tags and branches. there've been sufficient problems before when we've tried to use them to convince us that it really isn't worthwhile for this particular developmnt community. i should note that prumpf was one of the people who complained the loudest about the use of CVS tags.
Re: Incompatibility of PIC and non-PIC
In reply to a message not in the archiveQuoted 8 lines · Alan Modra
Quoted 5 lines · Matthew Wilcox
btw, is there any option to cvs diff which produces files which can be applied by any known version of patch? in my experience, patch can't find files specified by Index: lines _unless_ both the +++ and the --- files can't be found -- which is rarely the case with common names such as
Makefileor ChangeLog.
Quoted 6 lines
I haven't found one, and it's a real pain. I tend to edit patches covering multiple directories before passing them to patch.
"sed -e '/^[+-][+-]/d' <
cvs_diff_file| patch -p0 --posix" ought to work.Alan
Which versions of CVS are you using? CVS used to output diffs without including the directory path in the --- and +++ lines, but that's been fixed long ago. I don't have any problems with patch anymore.
-Tor
Re: Incompatibility of PIC and non-PIC
Quoted 3 lines · Tor Arntsen
Which versions of CVS are you using? CVS used to output diffs without including the directory path in the --- and +++ lines, but that's been fixed long ago. I don't have any problems with patch anymore.
You will if the diff contains files that exist in the root dir of your source tree and in subdirs, eg. Makefile.in and bfd/Makefile.in
Signature · 1 line
Linuxcare. Support for the Revolution.