On Mon, Nov 09, 2009 at 05:55:57PM -0500, APseudoUtopia wrote:
> On Sun, Nov 8, 2009 at 2:06 PM, Troels Kofoed Jacobsen
> wrote:
> > Hi all
> >
> > 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 re
On Sun, Nov 8, 2009 at 2:06 PM, Troels Kofoed Jacobsen
wrote:
> Hi all
>
> 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
On Sun, Nov 8, 2009 at 11:26 PM, Roman Neuhauser 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
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 c
Hi all
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.
Right now I'
