Date: Tue, 3 Jun 2003 12:10:44 -0500 From: "Kevin Kinsey, DaleCo, S.P." <kdk@daleco.biz> To: "Scott Rossillo" <scott@rossillo.net>, "Troy " <freebsd@untoldfaith.com> Cc: freebsd-newbies@freebsd.org Subject: Re: Three Quick Questions Message-ID: <000901c329f3$1343d470$7a41d5cc@nitanjared> References: <153207361.20030602155106@untoldfaith.com> <5.2.1.1.0.20030603091226.02b88e90@archimedes.rsn.bth.se> <44385.209.92.78.159.1054653923.squirrel@webmail.rossillo.net>
next in thread | previous in thread | raw e-mail | index | archive | help
To: "Troy " <freebsd@untoldfaith.com> Cc: <freebsd-newbies@freebsd.org> Sent: Tuesday, June 03, 2003 10:25 AM Subject: Re: Three Quick Questions > > At 15:51 2003-06-02 -0600, Troy wrote: > >>Hello, > >>Three quick questions here. > >>#3 > >>When upgrading via cvsup how do I tell what has changed to see if it > >> is worth upgrading after running the cvsup session? > > > > Save the output from cvsup. If you're using the GUI, just click the save > > button, and it will save in the "./cvsup.log" (or something like that). If > > you're using the command line cvsup, I cant recall any flag for output > > saves, but you can always use the script (man script) command, like so... > > > > # script /home/youruser/yourlog.file > > ...some info... > > # cvsup yourcvsupfile > > ...updating updating updating... > > # <ctrl-d> > > ...done... > > > > Now, check the /home/youruser/yourlog.file for changes and updates. > > > > HTH > > /Jalle or: #cvsup yourcvsupfile >& /home/youruser/yourlog.file & It's simple, works. Kevin Kinsey DaleCo, S.P.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?000901c329f3$1343d470$7a41d5cc>