Hi,
2010/12/15 Phil Holmes m...@philholmes.net:
Jan,
I think I can fix your LilyBuntu problem - I had the same. Try _installing_
LB, not running _live_ (I'm guessing this is what's happening - it was for
me). At the very initial text prompt, type install rather than live.
2010/12/15
On 12/16/10 7:24 PM, Janek Warchoł lemniskata.bernoull...@gmail.com
wrote:
3. Don't start with the hardest / highest-priority issues. Pick
something tagged with frogs to get started on.
Isn't that obvious? Along with the fact that i'd prefer to work on the
issues that bother me the most,
Hi,
I've read Issue classification and i think it would be good to add one
more guideline concerning priority: i believe that the priority should
depend on how widespread the issue is. Even minor problems concernning
some basic elements (that will probably happen many times in even a
single
On Wed 15 Dec 2010, 12:53 Janek Warchoł wrote:
Hi,
Hi!
I've read Issue classification and i think it would be good to add one
more guideline concerning priority: i believe that the priority should
depend on how widespread the issue is. Even minor problems concernning
some basic elements
- Original Message -
From: Janek Warchoł lemniskata.bernoull...@gmail.com
To: lilypond-devel lilypond-devel@gnu.org
Sent: Wednesday, December 15, 2010 11:53 AM
Subject: issue classification: priority guidelines
Hi,
I've read Issue classification and i think it would be good to add
On Wed, Dec 15, 2010 at 12:31:02PM -, Phil Holmes wrote:
- Original Message - From: Janek Warchoł
I've read Issue classification and i think it would be good to add one
more guideline concerning priority: i believe that the priority should
depend on how widespread the issue is.
2010/12/15 Graham Percival gra...@percival-music.ca:
In the mean time, go ahead and twiddle the definitions of
priorities (as long as you leave Critical alone). But be aware
that you're rearranging deck chairs on the titanic.
ROTFL -- my point exactly :-)
Cheers,
V.
On Wed, Dec 15, 2010 at 1:31 PM, Phil Holmes m...@philholmes.net wrote:
* Priority-High: An issue which produces output which does not accurately
reflect the input (e.g where the user would expect an accidental, but none
is shown) or which produces aesthetically poor output in a situation which
...@percival-music.ca
Cc: Janek Warchoł lemniskata.bernoull...@gmail.com; lilypond-devel
lilypond-devel@gnu.org
Sent: Wednesday, December 15, 2010 2:56 PM
Subject: Re: issue classification: priority guidelines
2010/12/15 Graham Percival gra...@percival-music.ca:
In the mean time, go ahead and twiddle
2010/12/15 Graham Percival gra...@percival-music.ca
Look, the ugly truth is that the priority field -- other than
critical -- has no effect on lilypond development. I've been
heavily involved since 2003 (before this issue tracker in 2006),
and that's my observation. It has no statistically
2010/12/15 Janek Warchoł lemniskata.bernoull...@gmail.com:
Ok, this means i have to fix some (lots of?) stuff myself (you got me
hooked perhaps, however i don't know how all this will turn out)...
Yes.
The following is for anyone interested in helping me in this task.
I have some basic
Janek
On 15/12/2010 15:32, Janek Warchoł wrote:
but i struggle with unbelieveably low VirtualBox
resolution - 800x600, it annoys me extremely on my big monitor. Maybe
i'll find an answer on the web
Look in the help.
9.6. Advanced display configuration
James
On 12/15/10 8:32 AM, Janek Warchoł lemniskata.bernoull...@gmail.com
wrote:
2010/12/15 Graham Percival gra...@percival-music.ca
Fighting about whether a bug should be high vs. low does NOTHING
to get it fixed sooner or later. This is a volunteer project, and
lilypond developers do not appear
13 matches
Mail list logo
