Nicolas P. M. Legrand wrote: > On Sun, May 09, 2010 at 08:17:29PM +0100, Jason McIntyre wrote: >> On Sun, May 09, 2010 at 04:49:26PM +0200, Nicolas P. M. Legrand wrote: >> > Hello, >> > >> > received the CDs on friday, a very nice moment as always, thanks >> > everyone :-). >> > >> > I saw minor typos in upgrade47.html while upgrading, useless prompt, >> > useless sudo and use of obsolete -F pkg_add flag: >> > >> > Index: upgrade47.html >> > =================================================================== >> > RCS file: /cvs/openbsd/www/faq/upgrade47.html,v >> > retrieving revision 1.8 >> > diff -u -r1.8 upgrade47.html >> > --- upgrade47.html 6 May 2010 01:36:59 -0000 1.8 >> > +++ upgrade47.html 9 May 2010 14:40:26 -0000 >> > @@ -553,7 +553,7 @@ >> > your $RELEASEPATH, run it with: >> > >> > <blockquote><pre> >> > -# <b>sudo sysmerge -s $RELEASEPATH/etc47.tgz -x >> > $RELEASEPATH/xetc47.tgz</b> >> > +<b>sysmerge -s $RELEASEPATH/etc47.tgz -x $RELEASEPATH/xetc47.tgz</b> >> > </pre></blockquote> >> > >> >> this should either be "#" or "$ sudo", i think, which is how we normally >> refer to prompts. i'm not sure whether that's a consistent faq thing too >> though. > > Sorry i didn't mention it has already been discussed for upgrade46.html: > > http://marc.info/?l=openbsd-misc&m=125696072511365&w=2 > > Nick then said: > > "Slapping a "sudo" in front > of everything they contribute to the FAQ is some people's style, > but not mine. And yes, the # in front is really annoying, since > much of upgrade46.html (including that line) is intended to be > copy/pasted. This is not true of most of the rest of the FAQ, where > I generally DON'T want people to copy/paste blindly and ignorantly."
couldn't have put it better myself. :) Actually, probably could have... > reading upgrade47.html for the first time, i thought it must be a sort > of copy/paste error and that I should mention it again. By the way > maybe there is a better way to mention those kind of problem than > posting on misc? misc@, www@, tech@ (though kinda pushing the lower-limits of good tech@ posting, but DOES include a diff, unlike all the bad tech@ postings :). I'll discourage sending only to me personally, on the grounds that sometimes I get busy and sometimes stuff falls through the cracks when that happens. :-/ Tried to figure out why that "issue" came back, but realized that the fix for 4.6 came AFTER I had created upgrade47.html, and I forgot to push it to 47. Ooops... (why I stay out of src/ ...) Nick.