Date: Mon, 9 Nov 2009 08:07:41 +0100 From: Troels Kofoed Jacobsen <tkjacobsen@gmail.com> To: Roman Neuhauser <neuhauser@sigpipe.cz> Cc: freebsd-questions@freebsd.org Subject: Re: Tracking commit messages from cli Message-ID: <6a3173850911082307i472e600dp111b6e9a83e85086@mail.gmail.com> In-Reply-To: <20091108222640.GH54137@isis.sigpipe.cz> References: <20091108190613.GA1486@photon.std> <20091108222640.GH54137@isis.sigpipe.cz>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, Nov 8, 2009 at 11:26 PM, Roman Neuhauser <neuhauser@sigpipe.cz> wrote: > On Sun, Nov 08, 2009 at 08:06:13PM +0100, Troels Kofoed Jacobsen wrote: >> With pkg_version I can easily see which installed ports has newer >> versions available, but what I miss is a way to see what has changed. >> The reason for this is that commit messages often say that only the >> pkg-plist has changed or something that does not make me want to update. > > ... > >> I know freshports exist, but I would rather not have to open a web >> browser. >> >> Does such a program exist or do I have to write my own. > > sorry to point out the obvious, but why not use svn (or cvs)? > As I said: "without having to track the whole tree". I know this would be a possibility, but would rather not use the convenience of portsnap. Also if the solution should be more usable for other people I would like it to be as simple as possible and not require so much overhead. Anyway, thanks for the answer -- maybe I'll just do that eventually. -- Med Venlig Hilsen Troels Kofoed Jacobsen
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6a3173850911082307i472e600dp111b6e9a83e85086>