On 12/06, Florian Pritz wrote:
On 05.12.2014 22:32, Bigby James wrote:
Thanks for clearing that up. Wasn't sure exactly what the development flow was
there.
--
A common mistake that people make when trying to design something completely
foolproof is to underestimate the ingenuity of complete
If this is on the wiki or elsewhere I've missed it, please feel free
to direct me there. What is the official policy on beta releases in
the mainline repositories? Is there one?
$ pacman -Ss | grep ^[a-z] | grep beta
core/grub 1:2.02.beta2-5
extra/foobillard++ 3.42beta-5
extra/frozen-bubble
Troy Engel wrote:
I'm specifically concerned about the choice to release betas of
freerdp into mainline and was trying to find out what the policy was
and when it was deemed OK to release betas. (as with grub). I am not
finding the reason for a freerdp upgrade documented to use the betas,
a
On Sat, Dec 6, 2014 at 1:38 PM, Antonio Rojas nqn7...@gmail.com wrote:
There are usually very specific reasons why beta packages are pushed to the
repos. For instance krecipes and krusader haven't seen a stable release for
5+ years and Sourceforge lists the betas as default download for both
On Fri, Dec 05, 2014 at 09:55:22AM -0600, Troy Engel wrote:
On Fri, Dec 5, 2014 at 3:53 AM, Magnus Therning mag...@therning.org wrote:
So, is there some way to configure mutt to go straight to the
gpg-agent, without any warning messages on startup?
I fought with this as soon as it came out
On 06/12/14 at 10:36pm, Magnus Therning wrote:
On Fri, Dec 05, 2014 at 09:55:22AM -0600, Troy Engel wrote:
On Fri, Dec 5, 2014 at 3:53 AM, Magnus Therning mag...@therning.org wrote:
So, is there some way to configure mutt to go straight to the
gpg-agent, without any warning messages on
6 matches
Mail list logo
