[OpenAFS] Re: Woah, it seems like it's working (1.3.77+ on
2.6.10)
Jeffrey Hutzelman
jhutz@cmu.edu
Thu, 20 Jan 2005 20:47:13 -0500
On Tuesday, January 18, 2005 09:47:26 +0000 William John Murray
<w.murray@rl.ac.uk> wrote:
> *) Getting the patches from the WWW archive was a pain. I
> had to save the page, rename it to xxx.patch, emacs it to discover
> that emacs will not edit patches (it knows they shouldn't be touched?)
> vi it to extract the patches, see they were for 1.3.77 but the email was
> about snap-14-01-05, sed all the changes, apply the patches, find that
> half of them did not work, sed s/-gt;/>/g, still the 'rlim' patch was
> not recognised by my system and I had to manually fix it, and then guess
> the 'small ftrace.c demangle' which Matthew referred to.
Note that there's nothing that says a patch needs to be named xxx.patch.
And yes, downloading patches as HTML is a pain, because you need to convert
HTML entities to the characters they represent. Note that in addition to
'>', you're also likely to find '<' and '&' encoded as entities.
If the patch you're interested in has been committed to CVS, you can use
CVSweb to examine and download the diffs for each file or for the whole
delta. It should be noted that a copy of the CVS repository can be found
in /afs/.grand.central.org/project/openafs/cvs
If the patch you're interested in was submitted to openafs-bugs, you can
download the patch from RT in a usable form. In general, folks who want to
publicly distribute patches that they are not going to submit to RT should
think about putting them somewhere on the web or in AFS.
-- Jeffrey T. Hutzelman (N3NHS) <jhutz+@cmu.edu>
Sr. Research Systems Programmer
School of Computer Science - Research Computing Facility
Carnegie Mellon University - Pittsburgh, PA