On Tue, Jun 23, 2015 at 7:12 AM, Justin Dray wrote:
> Hi,
>
> I was thinking it could be useful to show in comments when a new version is
> pushed by the maintainer of a package; just a line break and maybe v1 -> v2
> or the git commit message or something. It would be easier to make sense of
> c
On Tue, 23 Jun 2015 11:49:22 +0200
Marcel Korpel wrote:
> * Justin Dray (Tue, 23 Jun 2015 00:12:26 +):
> > I was thinking it could be useful to show in comments when a new
> > version is pushed by the maintainer of a package; just a line break
> > and maybe v1 -> v2 or the git commit message
* Justin Dray (Tue, 23 Jun 2015 00:12:26 +):
> I was thinking it could be useful to show in comments when a new
> version is pushed by the maintainer of a package; just a line break
> and maybe v1 -> v2 or the git commit message or something. It would
> be easier to make sense of comments on m
Might be irreverent to this topic, but we ArchlinuxCN community have this
tool `nvchecker`[1]
that can check updates of version numbers for packages.
It currently have support for pulling version infomation from aur4/aur,
github, pypi, and many other upsteam sources.
It records the current versio
On Mon, Jun 22, 2015 at 9:13 PM, Justin Dray wrote:
> Because that would only work for the current version, and back one, this
> way you could see the relevant change happening after an issue is reported
> and such. It seems like a much easier way to view the differences to me at
> least.
>
> - J
Why not just check the last updated date?
-- Eli Schwartz
Because that would only work for the current version, and back one, this
way you could see the relevant change happening after an issue is reported
and such. It seems like a much easier way to view the differences to me at
least.
- Just
On Mon, Jun 22, 2015 at 7:12 PM, Justin Dray wrote:
> Hi,
>
> I was thinking it could be useful to show in comments when a new version is
> pushed by the maintainer of a package; just a line break and maybe v1 -> v2
> or the git commit message or something. It would be easier to make sense of
> c
Hi,
I was thinking it could be useful to show in comments when a new version is
pushed by the maintainer of a package; just a line break and maybe v1 -> v2
or the git commit message or something. It would be easier to make sense of
comments on many of the packages I've seen and allow us to see if
