I saw a couple of messages, but no clarity. Is there a way to send SVG to
STDOUT?
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Output-SVG-to-STDOUT-tp181157.html
Sent from the Dev mailing list archive at Nabble.com.
___
lil
Weitergeleitete Nachricht
Betreff: [forge:site-support] #11241 Bug with issue import and <> in
summary
Datum: Tue, 15 Sep 2015 17:12:18 +
Von:John Barrett
Antwort an: [forge:site-support] <11...@site-support.forge.p.re.sf.net>
An: [forge:site-support] <11...
Hosada-san,
See my suggestions below.
(I hope they are correct).
https://codereview.appspot.com/262380043/diff/20001/Documentation/usage/running.itely
File Documentation/usage/running.itely (right):
https://codereview.appspot.com/262380043/diff/20001/Documentation/usage/running.itely#newcode4
Colin Campbell writes:
> On 2015-09-15 08:36 AM, Phil Holmes wrote:
>>
>> Don't really like the idea of an undefined status. If we don't go
>> for "invalid", perhaps another "closed" status of "abandoned" would
>> be better.
>>
>> --
>> Phil Holmes
>>
>
> Abandoned patches are a bit different f
On 2015-09-15 08:36 AM, Phil Holmes wrote:
Don't really like the idea of an undefined status. If we don't go for
"invalid", perhaps another "closed" status of "abandoned" would be
better.
--
Phil Holmes
Abandoned patches are a bit different from closed issues, IMO. It's
absolutely nece
Simon Albrecht writes:
> If a patch has been abandoned for lack of skill or time, Status should
> go back to Accepted. Though it can’t be said in general: if it has
> been abandoned because the developer decided it didn’t make sense, or
> if it has become obsolete through other development, then
Am 15.09.2015 um 15:39 schrieb David Kastrup:
Phil Holmes writes:
A comment and a question about the status field of the issues list.
Comment: with Google code, the status was automatically set to "Accepted"
for issues manually entered by a registered user. I see no reason for not
continuing
hello,
On 15/09/15 16:50, David Kastrup wrote:
> Simon Albrecht writes:
>
>> If a patch has been abandoned for lack of skill or time, Status should
>> go back to Accepted. Though it can’t be said in general: if it has
>> been abandoned because the developer decided it didn’t make sense, or
>> if
Thank you for your comments.
I've fixed some sentences.
https://codereview.appspot.com/262380043/diff/1/Documentation/usage/running.itely
File Documentation/usage/running.itely (right):
https://codereview.appspot.com/262380043/diff/1/Documentation/usage/running.itely#newcode478
Documentation/us
- Original Message -
From: "James"
To:
Sent: Tuesday, September 15, 2015 3:27 PM
Subject: Re: Issues list status
Hello,
On 15/09/15 13:57, Phil Holmes wrote:
A comment and a question about the status field of the issues list.
Comment: with Google code, the status was automaticall
Phil Holmes writes:
> A comment and a question about the status field of the issues list.
>
> Comment: with Google code, the status was automatically set to "Accepted"
> for issues manually entered by a registered user. I see no reason for not
> continuing this policy, but it does mean that bu
Hello,
On 15/09/15 13:57, Phil Holmes wrote:
> A comment and a question about the status field of the issues list.
>
> Comment: with Google code, the status was automatically set to "Accepted"
> for issues manually entered by a registered user. I see no reason for not
> continuing this policy,
A comment and a question about the status field of the issues list.
Comment: with Google code, the status was automatically set to "Accepted"
for issues manually entered by a registered user. I see no reason for not
continuing this policy, but it does mean that bug squad members (and
anyone el
Hosada-san,
See my comments below.
https://codereview.appspot.com/262380043/diff/1/Documentation/usage/running.itely
File Documentation/usage/running.itely (right):
https://codereview.appspot.com/262380043/diff/1/Documentation/usage/running.itely#newcode478
Documentation/usage/running.itely:47
14 matches
Mail list logo
