On Wed, Jul 11, 2012 at 05:48:48PM +0200, Janek Warchoł wrote:
> On Tue, Jun 26, 2012 at 10:55 PM, Graham Percival
> wrote:
> > To avoid slowing down programming to a crawl, I figure that we’ll
> > identify some subset of these regtests and have a separate make
> > regtests-quick command which onl
I will officially introduce this next Tuesday, but since it's now
a hot topic, let's have an extra round of discussion and fixing
before then.
http://lilypond.org/~graham/gop/gop_3.html
*** Summary
Let’s appoint David Kastrup as the “benevolent dictator” of the
stable/2.16 git branch.
*** Moti
On Fri, Jul 13, 2012 at 05:27:57PM +0200, David Kastrup wrote:
> Janek Warchoł writes:
> > And, above all, won't require the Release Manager to be an expert
> > programmer.
>
> Or communicator. Or look at recent issue reports more thoroughly than
> counting "Critical" labels to get an impression
http://codereview.appspot.com/6344092/diff/7001/input/regression/cross-staff-stems.ly
File input/regression/cross-staff-stems.ly (right):
http://codereview.appspot.com/6344092/diff/7001/input/regression/cross-staff-stems.ly#newcode2
input/regression/cross-staff-stems.ly:2:
Sorry, I was unclear.
On Sat, Jul 14, 2012 at 12:17:40AM +0200, Thomas Morley wrote:
> 2012/7/13 Phil Holmes :
> (...)
> > You can absolutely use different branches with lilydev. It's only more
> > difficult with lilygit. If you need help with creating and switching to
> > other branches, please shout.
>
> Is it ment
2012/7/13 Phil Holmes :
(...)
> You can absolutely use different branches with lilydev. It's only more
> difficult with lilygit. If you need help with creating and switching to
> other branches, please shout.
Is it mentioned in the CG? I didn't found it in the LilyDev-chapter.
Would be great if
On Fri, Jul 13, 2012 at 06:23:57PM +0100, Phil Holmes wrote:
> - Original Message - From: "Trevor Daniels"
>
>
> >a) a release-meister with responsibility to take all decisions.
> >That's what Han-Wen used to do, I believe. It worked
> >quite well, although Graham will have more of an in
2012/7/13 Phil Holmes :
(...)
> So - if your changes will break the snippet, but will only work in in future
> versions, copy the snippet to snippets/new and update it there.
Copy or cut and paste?
What about
%% and then run scripts/auxiliar/makelsr.py
?
-Harm
___
- Original Message -
From: "Thomas Morley"
To:
Cc: ;
Sent: Friday, July 13, 2012 10:17 PM
Subject: Re: parenthesizeStencil and bracketifyStencil (issue 6397043)
2012/7/13 :
Reviewers: ,
Message:
please review
Description:
parenthesizeStencil and bracketifyStencil
Issue 2646
Th
2012/7/13 Janek Warchoł :
> by the way,
>
> On Fri, Jul 13, 2012 at 10:14 PM, Thomas Morley
> wrote:
>> So I started from scratch:
>> - Amend previous commit
>> - Abort changes - Reset to origin
>> - LilyDev reboot
>> - made changes in files/added a new regtest
>> - New local commit
>> - Make patc
Janek Warchoł writes:
> On Fri, Jul 13, 2012 at 6:43 PM, David Kastrup wrote:
>> Janek Warchoł writes:
>
In particular since it would make those others feel like they count,
do something for the success of the project, and are part of a team
turning out code, decisions, and relea
On Fri, Jul 13, 2012 at 09:50:58PM +0200, Janek Warchoł wrote:
> On Fri, Jul 13, 2012 at 5:42 PM, David Kastrup wrote:
> > [ lots of travel info ]
>
> Thanks for tips! I'm not totally sure what my route will be, but i'll
> be glad if there'll be a chance to finish the journey in company :)
> Btw
2012/7/13 :
> Reviewers: ,
>
> Message:
> please review
>
> Description:
> parenthesizeStencil and bracketifyStencil
>
> Issue 2646
>
> These function can parenthesize/bracketify nearly all kind of stencils.
>
> Please review this at http://codereview.appspot.com/6397043/
>
> Affected files:
> M
Reviewers: ,
Message:
please review
Description:
parenthesizeStencil and bracketifyStencil
Issue 2646
These function can parenthesize/bracketify nearly all kind of stencils.
Please review this at http://codereview.appspot.com/6397043/
Affected files:
M Documentation/ly-examples/aucun-snipp
On Fri, Jul 13, 2012 at 6:43 PM, David Kastrup wrote:
> Janek Warchoł writes:
>> Obviously, Graham would like to "dumb down" the rules as much as
>> possible indeed (as long as he is the Release Manager it means less
>> work for him). But he didn't say that the rules *must* be 100%
>> dumbed-dow
by the way,
On Fri, Jul 13, 2012 at 10:14 PM, Thomas Morley
wrote:
> So I started from scratch:
> - Amend previous commit
> - Abort changes - Reset to origin
> - LilyDev reboot
> - made changes in files/added a new regtest
> - New local commit
> - Make patch set
ouch. Too bad that (as far as i
2012/7/13 Thomas Morley :
> 2012/7/13 Thomas Morley :
> (...)
>> Seems all ok so far (patch attached)
> (...)
>
> Forgot the attachment.
Just noticed a copy/paste error in the patch. It will produce nonsense.
Next try tomorrow.
___
lilypond-devel mailin
(WARNING: non-linear quote)
On Fri, Jul 13, 2012 at 10:14 PM, Thomas Morley
wrote:
> Now I'm totally puzzled and confused.
Looks that git-cl tried to upload to sever named 'git cl upload
origin/master' - no way this could work:
> harm@harm-laptop ~/lilypond-git (dev/local_working)$ git cl uploa
2012/7/13 Thomas Morley :
(...)
> Seems all ok so far (patch attached)
(...)
Forgot the attachment.
0001-parenthesizeStencil-and-bracketifyStencil.patch
Description: Binary data
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.o
2012/7/13 Janek Warchoł :
> On Fri, Jul 13, 2012 at 8:32 PM, Phil Holmes wrote:
>>
>>> 2012/7/13 Trevor Daniels :
Phil Holmes wrote Friday, July 13, 2012 5:56 PM
> Run the command
>
> git cl issue 6352049
>>>
>>> Dosn't work. :(
>>
>> It really should do.
>
> Wasn't 6352049 t
On Fri, Jul 13, 2012 at 5:42 PM, David Kastrup wrote:
> [ lots of travel info ]
Thanks for tips! I'm not totally sure what my route will be, but i'll
be glad if there'll be a chance to finish the journey in company :)
Btw, should i prepare myself linguistically? My German is /very/
rusty... i h
On Fri, Jul 13, 2012 at 8:32 PM, Phil Holmes wrote:
>
>> 2012/7/13 Trevor Daniels :
>>>
>>> Phil Holmes wrote Friday, July 13, 2012 5:56 PM
Run the command
git cl issue 6352049
>>
>> Dosn't work. :(
>
> It really should do.
Wasn't 6352049 the number Harm *didn't* want to use?
i gu
- Original Message -
From: "Thomas Morley"
To: "Trevor Daniels"
Cc: "Phil Holmes" ; "lilypond-devel"
Sent: Friday, July 13, 2012 6:27 PM
Subject: Re: Problem with uploading patch
2012/7/13 Trevor Daniels :
Phil Holmes wrote Friday, July 13, 2012 5:56 PM
From: "Thomas Morley"
Thomas Morley writes:
> Hi,
>
> I tried to upload a patch related to issues 2646 and 1523.
>
> Surprisingly (for me) it was added to: Issue 6352049: which-page (Closed)
>
> Obviously I did sth wrong and/or missed a step.
You used the same branch as last time without resetting the issue.
Try
"Phil Holmes" writes:
> - Original Message -
> From: "Trevor Daniels"
> To: "David Kastrup" ; "Janek Warchoł"
>
> Cc:
> Sent: Friday, July 13, 2012 6:08 PM
> Subject: Re: clear policy discussions
>
>
>> a) a release-meister with responsibility to take all decisions.
>> That's what Han
"Trevor Daniels" writes:
> David Kastrup wrote Friday, July 13, 2012 4:27 PM
>
>
>> Janek Warchoł writes:
>>
>>> This is important, too, because Graham won't always be the Project
>>> Manager. It's also not guaranteed that there'll always be an
>>> experienced developer with sufficient time to
2012/7/13 Trevor Daniels :
>
> Phil Holmes wrote Friday, July 13, 2012 5:56 PM
>
>
>> From: "Thomas Morley"
>>
>>> What should I do?
>>
>> Run the command
>>
>> git cl issue 6352049
>>
>> and then repeat
>>
>> git cl upload
>>
>> git cl needs to be told the issue number on Rietveld, if it's differ
- Original Message -
From: "Trevor Daniels"
To: "David Kastrup" ; "Janek Warchoł"
Cc:
Sent: Friday, July 13, 2012 6:08 PM
Subject: Re: clear policy discussions
a) a release-meister with responsibility to take all decisions.
That's what Han-Wen used to do, I believe. It worked
quit
Phil Holmes wrote Friday, July 13, 2012 5:56 PM
> From: "Thomas Morley"
>
>> What should I do?
>
> Run the command
>
> git cl issue 6352049
>
> and then repeat
>
> git cl upload
>
> git cl needs to be told the issue number on Rietveld, if it's different from
> the most recent.
Or use a f
David Kastrup wrote Friday, July 13, 2012 4:27 PM
> Janek Warchoł writes:
>
>> This is important, too, because Graham won't always be the Project
>> Manager. It's also not guaranteed that there'll always be an
>> experienced developer with sufficient time to handle release tasks.
>
> I just d
- Original Message -
From: "Thomas Morley"
To: "lilypond-devel"
Sent: Friday, July 13, 2012 5:44 PM
Subject: Problem with uploading patch
Hi,
I tried to upload a patch related to issues 2646 and 1523.
Surprisingly (for me) it was added to: Issue 6352049: which-page (Closed)
Obviou
Hi,
I tried to upload a patch related to issues 2646 and 1523.
Surprisingly (for me) it was added to: Issue 6352049: which-page (Closed)
Obviously I did sth wrong and/or missed a step.
log:
harm@harm-laptop ~$ cd lilypond-git/
harm@harm-laptop ~/lilypond-git (dev/local_working)$ git add
input/r
Janek Warchoł writes:
> On Fri, Jul 13, 2012 at 5:27 PM, David Kastrup wrote:
>> Janek Warchoł writes:
>>> Graham's focus is on transparent /rules/ that are easy to follow, and
>>> preferably won't lay *too* much responsibility on Release Manager's
>>> shoulders.
>>
>> To be exact: none.
>>
>>>
On Fri, Jul 13, 2012 at 5:27 PM, David Kastrup wrote:
> Janek Warchoł writes:
>> Graham's focus is on transparent /rules/ that are easy to follow, and
>> preferably won't lay *too* much responsibility on Release Manager's
>> shoulders.
>
> To be exact: none.
>
>> And, above all, won't require the
Janek Warchoł writes:
> David Kastrup wrote:
>> [ let's make a LilyPond meeting ]
>
> So, is the date ultimately set? (Friday the 24th to Tuesday the 28th?)
> I confirm my presence with 98% certainty (2% are reserved for
> earthquakes, falling meteorites, bus/train strikes and illness)
> for at
Janek Warchoł writes:
> i said that i'll post an answer to this thread, so here it is :)
>
> David and Graham are clearly speaking from two different points of
> view. Or, to be (hopefully) more accurate, they are on two orthogonal
> planes.
>
> David is an experienced developer. He can judge L
David Kastrup wrote:
> [ let's make a LilyPond meeting ]
So, is the date ultimately set? (Friday the 24th to Tuesday the 28th?)
I confirm my presence with 98% certainty (2% are reserved for
earthquakes, falling meteorites, bus/train strikes and illness)
for at least 3 days, but hopefully all 5 of
Hi,
i said that i'll post an answer to this thread, so here it is :)
David and Graham are clearly speaking from two different points of
view. Or, to be (hopefully) more accurate, they are on two orthogonal
planes.
David is an experienced developer. He can judge LilyPond code better
than many o
One difficulty I've discovered - locating convert-ly. I'm continuing
other testing.
http://codereview.appspot.com/6352053/diff/6008/scripts/auxiliar/makelsr.py
File scripts/auxiliar/makelsr.py (left):
http://codereview.appspot.com/6352053/diff/6008/scripts/auxiliar/makelsr.py#oldcode7
scripts/
Werner LEMBERG writes:
>>> It is very unfortunate that we can't upgrade to the current
>>> texinfo.tex file; it contains a lot of improvements, including a
>>> very flexible URL command.
>>
>> Why can't we? If it is ok for us to distribute a modified version
>> of texinfo.tex, I am pretty sure
On Fri, Jul 13, 2012 at 11:07:57AM +0100, Phil Holmes wrote:
> Would I be right in saying that in scheme files (a) (define lines
> should always be left-justified (no space before) and (b) indents
> should always be 2 spaces and never tabs?
Unfortunately not. The current situation for scheme is:
Please review
http://codereview.appspot.com/6344092/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
>> It is very unfortunate that we can't upgrade to the current
>> texinfo.tex file; it contains a lot of improvements, including a
>> very flexible URL command.
>
> Why can't we? If it is ok for us to distribute a modified version
> of texinfo.tex, I am pretty sure that I can concoct a fix for
>
>> this-is-a-very
>> -long-name.ly
>
> No, I don't like that idea. Filenames shouldn't be hyphenated.
I disagree. By starting a line with the hyphen it is clear that it is
part of the file name and not due to hyphenation (and we use a
typewriter font also). It is *much* less ugly than ove
"Phil Holmes" writes:
> - Original Message -
> From: "David Kastrup"
> To:
> Sent: Friday, July 13, 2012 11:18 AM
> Subject: Re: Whitespace and scheme
>
>
>> "Phil Holmes" writes:
>>
>>> Would I be right in saying that in scheme files (a) (define lines
>>> should always be left-justif
- Original Message -
From: "David Kastrup"
To:
Sent: Friday, July 13, 2012 11:18 AM
Subject: Re: Whitespace and scheme
"Phil Holmes" writes:
Would I be right in saying that in scheme files (a) (define lines
should always be left-justified (no space before)
No, just top level def
"Phil Holmes" writes:
> Would I be right in saying that in scheme files (a) (define lines
> should always be left-justified (no space before)
No, just top level defines, like everything at top level. Top level is
when the preceding part of the file has matched opening and closing
parens. Rough
Would I be right in saying that in scheme files (a) (define lines should
always be left-justified (no space before) and (b) indents should always be
2 spaces and never tabs?
I'm looking at music-functions.scm and it has tabs and non-left defines.
--
Phil Holmes
_
- Original Message -
From: "Graham Percival"
To: "David Kastrup"
Cc:
Sent: Friday, July 13, 2012 12:40 AM
Subject: Re: Texinfo help, please
On Wed, Jul 11, 2012 at 10:45:24PM +0200, David Kastrup wrote:
Graham Percival writes:
> Hmm. So there's absolutely no way to get
>
> -
Well, I found it so ugly the Segno in the staff does not cooperate with the
\repeat volta command.
I installed on my WIN7 offline computer the lilydef VM, got a tarball from
GIT (HTML user interface), and tested my ideas to change it.
In contact with harm6 and Marc Hohl on this toppic, I had a l
Graham Percival writes:
> On Fri, Jul 13, 2012 at 08:01:52AM +0200, David Kastrup wrote:
>> Graham Percival writes:
>>
>> > Sorry, I should have specified "absolutely no way to get ---
>> > without any mixing of content and layout commands". I think we
>> > should minimize any layout-specific
LGTM
http://codereview.appspot.com/6345086/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
http://codereview.appspot.com/6344092/diff/1/Documentation/snippets/new/cross-staff-stems.ly
File Documentation/snippets/new/cross-staff-stems.ly (right):
http://codereview.appspot.com/6344092/diff/1/Documentation/snippets/new/cross-staff-stems.ly#newcode5
Documentation/snippets/new/cross-staff-
53 matches
Mail list logo
