On 01/22/2015 03:51 PM, Vesa wrote: > Should already be fixed in the stable-1.1 branch. > > ------------------------------------------------------------------------------ > New Year. New Location. New Benefits. New Data Center in Ashburn, VA. > GigeNET is offering a free month of service with a new server in Ashburn. > Choose from 2 high performing configs, both with 100TB of bandwidth. > Higher redundancy.Lower latency.Increased capacity.Completely compliant. > http://p.sf.net/sfu/gigenet > _______________________________________________ > LMMS-devel mailing list > LMMS-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/lmms-devel Great, is this only for 1.1.0 then? I updated via a watch file
version=3 opts="filenamemangle=s/(?:.*)?v?(\d[\d\.]*)\.tar\.gz/lmms-$1.tar.gz/" \ https://github.com/LMMS/lmms/tags/ (?:.*/)?v?(\d[\d\.]*)\.tar\.gz So, it looks for v tags and downloads that and merges the code... Will there be a new version you put out to fix this? I wanted to try to avoid mistakenly using unreleased versions... will uscan ing github for new releases cause issues, should I change to scanning lmms.io instead to get the proper release? -- Regards ------------------------------------------------------------------------------ New Year. New Location. New Benefits. New Data Center in Ashburn, VA. GigeNET is offering a free month of service with a new server in Ashburn. Choose from 2 high performing configs, both with 100TB of bandwidth. Higher redundancy.Lower latency.Increased capacity.Completely compliant. http://p.sf.net/sfu/gigenet _______________________________________________ LMMS-devel mailing list LMMS-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lmms-devel
