Re: ’Pond Jobs & Their Descriptions

Hi Kieren, czw., 6 lut 2020 o 00:55 Kieren MacMillan napisał(a): > Hello all! > > I’m curious as to all the various jobs/tasks required to keep Lilypond > development moving forward at the fastest possible pace and in the most > efficient possible way. Is there a single list compiled anywhere, w

[RFC] weekly dev chats

Hello, I just got inspired by the Agile Manifesto Principles[1], specifically: > The most efficient and effective method of > conveying information to and within a development > team is face-to-face conversation. This reminded me how dynamic, positive and motivating were the LP talks in Salzburg.

Re: RFC: docker for CI

In principle, thumbs up. However, I think it's essential that we don't try to do too much at once; I'd suggest to focus on one most important aspect first. To do that, I'd like to ask a helper question: what are 2 most important reasons for using Docker instead of Patchy? In other words, what are 2

Re: RFC: docker for CI

sob., 8 lut 2020 o 23:30 Janek Warchoł napisał(a): > In principle, thumbs up. However, I think it's essential that we don't try > to do too much at once; I'd suggest to focus on one most important aspect > first. To do that, I'd like to ask a helper question: what a

Re: [RFC] Commit message format

+1 to all parts of the proposal from me. pt., 7 lut 2020 o 16:39 Han-Wen Nienhuys napisał(a): > Currently, on push most our commit messages look like: > > Issue XXX: Subject > > Body > Body > > > There are a couple of downsides to this format: > > * The number takes up space in the >

Re: [RFC] weekly dev chats

sob., 8 lut 2020 o 23:56 David Kastrup napisał(a): > Janek Warchoł writes: > > I'd be willing to organize and moderate the meetings (take care of > > preparing the agenda and sharing the take-aways with the devel list). I > > know that it'd be a challenge to

Re: Add Code of Conduct

Elaine, pt., 7 lut 2020 o 02:28 Flaming Hakama by Elaine napisał(a): > 1) "Adopt this CoC or I will leave the community" Such threats amount to a > my-way-or-the-highway attitude, which is an attempt to enforce veto power > in what is supposed to be a collaborative / concensus / democratic > ap

Re: Add Code of Conduct

+1 to everything Harm said, and big thanks to Werner! (and Urs, who co-organized Salzburg event) Janek sob., 8 lut 2020 o 16:52 Thomas Morley napisał(a): > Am Sa., 8. Feb. 2020 um 14:59 Uhr schrieb Kieren MacMillan > : > > > To me, the greatest shame is that all the positive energy and momentum

Re: Add Code of Conduct

niedz., 9 lut 2020 o 00:39 David Kastrup napisał(a): > David Kastrup writes: > > > Janek Warchoł writes: > > > >> Elaine, > >> > >> pt., 7 lut 2020 o 02:28 Flaming Hakama by Elaine < > ela...@flaminghakama.com> > >> napisał(a): >

Re: Add Code of Conduct

James, first, I am sorry that you are so disturbed. I realize that this is partially my fault, so I apologize. sob., 8 lut 2020 o 09:23 James Lowe napisał(a): > On 07/02/2020 09:50, Han-Wen Nienhuys wrote: > > Thanks for your careful observations. > > > > First, the CoC was actually coined by M

Re: Add Code of Conduct [Another RFC or not now?]

Graham, sob., 8 lut 2020 o 21:23 Graham Percival napisał(a): > I don't have any reasons that haven't been mentioned already, > other than one meta-reason: proposals like this are very divisive. > Trying to have this discussion in the middle of a "final sprint > towards 2.20" was unfortunate. >

Re: ’Pond Jobs & Their Descriptions

Kieren, I see that I've misunderstood you - I apologize. My LP time today is over, so I'll follow on this topic on the next occasion :) sob., 8 lut 2020 o 23:31 Kieren MacMillan napisał(a): > Hi Janek, > > > I appreciate the initiative, and I agree that we could use a clearer > view on the resp

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

niedz., 9 lut 2020 o 00:31 napisał(a): > On 2020/02/08 22:57:13, janek wrote: > > Because of significant disagreement, and to ensure that LilyPond > contributors > > don't feel pushed, I am hereby officially withdrawing this proposal. I > apologize > > for the disturbance caused by the way I have

Long time no see :-)

Hello, does anyone remember me? :-) Looks like I'm going to meddle a tiny bit in the Pond affairs again. What you've been up to in the last 4 years? What's the current situation? cheers, Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https

Re: Long time no see :-)

ave, but... I'd like to, as well. wt., 20 lis 2018 o 00:28 Thomas Morley napisał(a): > Hi Janek :)) > Am Mo., 19. Nov. 2018 um 20:47 Uhr schrieb Janek Warchoł > : > > What you've been up to in the last 4 years? What's the current situation? > > As Werner

New LilyPond contributor: Basia Mroczek

Hi everyone, I'd like to introduce Basia Mroczek, who's joining our team for several months. Basia is a graduate (is that the correct english term?) of Mathematics at the University of Warsaw (so, cream of the crop!) who'd like to steer her career more towards programming rather than math. She's

Re: New LilyPond contributor: Basia Mroczek

czw., 22 lis 2018 o 00:21 Werner LEMBERG napisał(a): > I suggest to start with setting up a build environment (on GNU/Linux > box or in a virtual GNU/Linux machine) so that changes to C++ code, > Scheme code, and documentation can be easily done. > Yeah, we're working on that. :) czw., 22 lis

Re: New LilyPond contributor: Basia Mroczek

Hello, czw., 22 lis 2018 o 13:58 Torsten Hämmerle napisał(a): > Welcome, Basia, and > welcome back, Janek! > > Good to see young people joining the flock. :) > > @Karlin: > Basia is a Polish affectionate/familiar form of Barbara. > It is pronounced "Basha", similar to Masha or Sasha, just with a

Re: New LilyPond contributor: Basia Mroczek

pt., 23 lis 2018 o 10:15 Urs Liska napisał(a): > Am 23.11.18 um 00:08 schrieb Janek Warchoł: > > Whoah, I almost forgot them :p > So, you're still using them? > > Unfortunately not. I really used them because it's so convenient to > maintain multiple builds fro

Janek is coming back to LilyPond! :-)

Hi everyone, for those who don't know me: I was an active member of the community several years ago, contributed patches, co-authored LilyPond blog, and together with Urs Liska typeset an award-winning publication

Plan for improving contribution process

Hello, Let's start with a high-level plan, and identify what are the biggest problems. Here's a document where I started; I'll give edit access to each of you upon request. https://docs.google.com/document/d/1zYwygWEKJt21rl-bKL41IpjFmiBjlfob6eS63jd-62I/edit?usp=sharing best, Janek PS I know tha

Re: Janek is coming back to LilyPond! :-)

nto chunks, to limit the amount of stuff "in progress". my best wishes to you, Janek pon., 20 sty 2020 o 17:34 Janek Warchoł napisał(a): > Hi everyone, > > for those who don't know me: I was an active member of the community > several years ago, contributed patches, co

Re: Janek is coming back to LilyPond! :-)

wt., 21 sty 2020 o 19:33 Kieren MacMillan napisał(a): > 1. Wonderful to have you back! > 2. There’s this lyrics thing maybe you could take a look at…? ;) :-) Hopefully it can be one of the next things I work on. But contributing process must come first. J

Re: development process

I've just went through the patch upload process (for proposed Code of Conduct https://codereview.appspot.com/575620043/) and I agree that it should be changed. It was obscure and confusing even for me. cheers, Janek wt., 4 lut 2020 o 22:57 Han-Wen Nienhuys napisał(a): > As promised in several c

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

Hi, śr., 5 lut 2020, 00:34 użytkownik napisał: > What problem are we trying to solve here? > In short, it's been found (I think Mike will be able to give you specific examples) that having code of conduct encourages contributions from newcomers. Also, it's simply good to have a lightweight pro

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

Hi Jonas, śr., 5 lut 2020 o 09:18 napisał(a): > Not having read any of this, I strongly suggest that this is discussed > on lilypond-devel _before_ anything is brought to review. Discussion on > GitHub is fine, but I for one wasn't aware that there is one! > Thank you for being open. I consider

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

I'll try to speak only on the most pressing points to avoid bloating the discussion unnecessarily. śr., 5 lut 2020 o 14:41 David Kastrup napisał(a): > Janek Warchoł writes: > > In short, it's been found (I think Mike will be able to give you specific > > examples) th

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

śr., 5 lut 2020 o 23:47 Kieren MacMillan napisał(a): > I guess what confuses me about this whole discussion/thread — starting > with the Salzburg "roundtable", really — is how quickly it appears to > escalate from "let’s collaboratively design an ecosystem where everyone can > be in their Zone(s)

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

6 lut 2020 o 00:32 Janek Warchoł napisał(a): > Do you think that approaching other people with suspicion like this (i.e. > expecting they have worst intentions, which is getting close to a > conspiracy theory) contributes to a friendly atmosphere? I don't think so. > I reali

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

David, czw., 6 lut 2020, 02:55 użytkownik David Kastrup napisał: > Not everybody likes to argue. So yes, I felt in a comfortable space > with you and it was a productive exchange where I was not aware of any > potential for controversy. But I'll agree that it sends an awful > message to bystan

Re: Add Code of Conduct (issue 575620043 by janek.lilyp...@gmail.com)

Werner, czw., 6 lut 2020, 03:46 użytkownik Werner LEMBERG napisał: > > > The preamble and intent is one thing; adding a corrective committee > > with the authority to enact punishments based on anonymous reports > > is another. It implements hierarchies and institutions exerting > > coercive po

chord naming

Hi, I'm from Poland and we use here a different chord naming convention: the main difference is that minor chords are written with lowercase and major chords are written with uppercase. I'd like to add this to Lily. I found .ly files with alternative note names (used in other languages) in \LilyPo

Re: chord naming

W dniu 22 października 2010 16:47 użytkownik Carl Sorensen < c_soren...@byu.edu> napisał: > On 10/22/10 5:08 AM, "Janek Warchoł" > wrote: > > > Hi, > > I'm from Poland and we use here a different chord naming convention: the > main > > differe

issue classification: priority guidelines

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 score)

Re: issue classification: priority guidelines

2010/12/15 Graham Percival > 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 significant > affe

Re: issue classification: priority guidelines

010/12/15 Graham Percival : > > 2010/12/15 Janek Warchoł : >> i struggle with 800x600 VirtualBox resolution > > Answer is in the CG in version 2.13.43.  Look at the lilybuntu page right now. Indeed, i used to run lilybuntu live instead of installing it and then running it from

Re: flags, beams and stem length in forced directions - output improvement

W dniu 27 grudnia 2010 14:02 użytkownik James Lowe napisał: > > > 2010/12/27 Janek Warchoł : > > - in the first line: the stems of the b's are too short, > > Janek, > > See http://lists.gnu.org/archive/html/lilypond-devel/2010-04/msg00085.html > > I believe t

Re: flags, beams and stem length in forced directions - output improvement

2010/12/27 James Lowe : > > 2010/12/27 Janek Warchoł : > > "the same kind of discussion" - do you mean that it's bad idea to > > touch this issue because it will lead to pointless academical > > disputes? > > No not at all, I was merely point out that t

Re: flags, beams and stem length in forced directions - output improvement

2010/12/27 Carl Sorensen : > Janek, > > I appreciate your work.  And I appreciate your raising the issue. > (...) [But] > The *only* way for you to guarantee it is solved is for *you* to do the work. That's exactly what i expect! I'll try to solve it, as hard as i can. (The only thing that worries

Re: flags, beams and stem length in forced directions - output improvement

2010/12/27 Carl Sorensen : > On 12/27/10 7:38 AM, "Janek Warchoł" > wrote: >> That's exactly what i expect! I'll try to solve it, as hard as i can. >> (The only thing that worries me is that my programming skills are not >> high... i only hope that

Re: flags, beams and stem length in forced directions - output improvement

2010/12/27 Carl Sorensen : > On 12/27/10 9:01 AM, "Janek Warchoł" > wrote: >> i understand that your answer to this particular question is "compress >> the flag" in case of downstem notes :) > > No, that is not my answer.  I don't have an a

Re: including gregorian.ly breaks lyrics alignment in melismas

t changing the way it works, because it causes bad files to be easily produced: just a few days ago Michael Dykes posted a question about the attached piece (in "Not enough space between certain words" thread). Obviously he didn't know about the need to revert packed-spacing, which

Re: flags, beams and stem length in forced directions - output improvement

2010/12/27 Han-Wen Nienhuys > Why don't you try to find some scans of reputable editions to see what > the standard behavior is in this case? Because i believe the situation is quite different. Would it be feasible for an engraver to have different flags for many different stem lengths? No, perha

Re: including gregorian.ly breaks lyrics alignment in melismas

2010/12/28 Trevor Daniels > > Janek Warchoł wrote Tuesday, December 28, 2010 3:28 PM >> I wouldn't describe this behaviour as "packing notes as tightly as >> possible" - the first note gets enormous amount of space. Don't you >> think that packed-spacin

Re: flags, beams and stem length in forced directions - output improvement

2010/12/31 Carl Sorensen : > > On 12/29/10 4:32 PM, "Janek Warchoł" > wrote: >> I prefer B because it is the most balanced one - the 16ths don't look >> cramped, and the 8ths don't look 'airy' when compared to 16ths >> (especially the be

illness

Dear Team, i see that some very interesting things are happening. I was inactive in the last days because i've contracted pneumonia, argh... >:-[ I hope to participate a bit in the discussions, but not as much as i'd like to. best, Janek ___ lilypond-d

Re: Meeting 2nd half of August!

On Wed, Jun 27, 2012 at 8:19 PM, Graham Percival wrote: > Having never used scheme or C++ in > lilypond to fix a bug, I'm curious to find out how it's done. The Graham Way of fixing bugs: mark the issue as Invalid ;-) ___ lilypond-devel mailing list li

Re: Meeting 2nd half of August!

On Tue, Jun 26, 2012 at 6:26 PM, David Kastrup wrote: > [...] > So the core data would be "Dortmund Germany" (about 10 miles from there) > and the proposal for a date would Friday August 17th to Tuesday August > 21st, or one week later. Excellent! Both options are ok to me, with a small preferen

Re: illness

On Thu, Jun 28, 2012 at 11:39 PM, Graham Percival wrote: > On Thu, Jun 28, 2012 at 08:46:09PM +0200, Janek Warchoł wrote: >> i see that some very interesting things are happening. >> I was inactive in the last days because i've contracted pneumonia, argh... >> >:-[ &

Re: illness

On Fri, Jun 29, 2012 at 10:54 PM, Valentin Villenave wrote: > On Thu, Jun 28, 2012 at 8:46 PM, Janek Warchoł > wrote: >> I was inactive in the last days because i've contracted pneumonia, argh... >> >:-[ >> I hope to participate a bit in the discussions, bu

Re: Gets vertical skylines from grob stencils (issue 5626052)

Hi all, my favorite patch returned! Yay! I did some testing and the results are here: http://lilypond-stuff.1065243.n5.nabble.com/file/n5705594/patchset37-results.tar.gz (sorry, too big for an attachment - 200 kB) In short: - staffswitch lines are broken - barnumbers collide with ties - some ties

make bin got dumb because of "Fix description in lily/include/smobs.hh"

Hi, until recently, 'make bin' was a very smart tool: it recompiled only necessary .cc files, not everything. That was lifesaving: instead of having to wait for 5 minutes, i got the results of my changes in 5 seconds. Unfortunately, this is no longer the case: no matter how trivial the change, m

Re: make bin got dumb because of "Fix description in lily/include/smobs.hh"

On Tue, Jul 3, 2012 at 7:35 PM, David Kastrup wrote: > So obviously something else is wrong here. Try removing > lily/out/smobs.dep and lily/out/smobs.o and see whether this helps. > > To be expected is a large amount of recompilation _once_ since a lot of > files need smobs.hh. If it occurs rep

Re: make bin got dumb because of "Fix description in lily/include/smobs.hh"

On Tue, Jul 3, 2012 at 8:55 PM, Janek Warchoł wrote: > Now comes the most surprising part: just to make sure, i just did the > following: > checkout origin/master # local master contained a revert of that commit > make from scratch > add a trivial change > make bin ...su

Re: make bin got dumb because of "Fix description in lily/include/smobs.hh"

On Tue, Jul 3, 2012 at 10:19 PM, David Kastrup wrote: > It is almost certainly a problem with your system clock. If you have > touched source files with a future clock, and now the clock is right, > then compiled files will be outdated ("older" than the source file) > immediately after compilatio

Re: Gets vertical skylines from grob stencils (issue 5626052)

On Mon, Jul 2, 2012 at 1:03 AM, wrote: > I did a quick test on some music. > Ledger lines might not be getting the space they need. In rare cases, > all the systems were overlaid on the top of the page. Several objects > might need an increase in their defaul

Re: Gets vertical skylines from grob stencils (issue 5626052)

On Wed, Jul 4, 2012 at 11:31 AM, m...@apollinemike.com wrote: > Thanks Janek! Very valuable stuff. :) >> (sorry, too big for an attachment - 200 kB) >> In short: >> - staffswitch lines are broken > > This is because VoiceFollower is not set as (cross-staff . #t) in > define-grobs.scm. I'm not

Re: Help with git rebase recovery, please

On Wed, Jul 4, 2012 at 4:00 PM, Graham Percival wrote: > On Wed, Jul 04, 2012 at 02:55:19PM +0100, Phil Holmes wrote: >> If you're not quite sure of the changes you want to make, can you >> get help with >> >> git reset --hard "HEAD@{10 minutes from now} >> >> ? :-) > > That only works on Janek's

why don't align to x-extent of a Paper_column?

Hi, as i'm working with grob alignment, i've stumbled upon if (Paper_column::has_interface (him)) return scm_from_double (0.0); in Self_alignment_interface::aligned_on_parent - I'm not sure what is its purpose. This was introduced by Han-Wen's commit ebb1f1f12ab21af1d365a635aa17e39e47a7c2b5

Re: Gets vertical skylines from grob stencils (issue 5626052)

On Wed, Jul 4, 2012 at 3:36 PM, m...@apollinemike.com wrote: > >> No idea when i'll have time to finish Tie Report, but as tie shapes >> are screwed in general, i wouldn't care much about this change. New >> shape isn't worse than previous one, i'd say. > > I think that there's supposed to be a b

Re: why don't align to x-extent of a Paper_column?

On Thu, Jul 5, 2012 at 3:07 PM, Han-Wen Nienhuys wrote: > On Wed, Jul 4, 2012 at 2:34 PM, Janek Warchoł > wrote: >> Hi, >> >> as i'm working with grob alignment, i've stumbled upon >> >> if (Paper_column::has_interface (him))

Re: Gets vertical skylines from grob stencils (issue 5626052)

On Thu, Jul 5, 2012 at 5:23 PM, m...@apollinemike.com wrote: > New patch set up that fixes all of the problems Janek pointed out I confirm, but the fun doesn't end yet :P \relative f' { c4( d e f) g1 } \addlyrics { bl lah } \relative f'' { c4( b a g) f1 } \addlyrics { bl lah } \relativ

\tweak inside Lyrics - is tweaking LyricHyphens unsupported?

Hi all, recently David allowed \tweak to be used in Lyrics context, and allowed to use additional parameter for modifying indirect grobs. Armed with that, i hoped to achieve the result of this: { \repeat unfold 4 c'16 } \addlyrics { The \once \override LyricHyphen #'minimum-distance = #4 peo -- p

Re: 2.15.41 Regtests

On Sun, Jul 8, 2012 at 4:56 PM, Phil Holmes wrote: > http://www.philholmes.net/lilypond/regtestresults/ > > Please look at it and see if these are intended changes. beam-beat-grouping - no idea if its intended, but new version looks better than old one to me changed forte seems ok collision-head-

Re: Regression test rater

On Sat, Jun 30, 2012 at 3:33 PM, Phil Holmes wrote: > First of all, thanks to those who have spent time and energy rating the > regression test at http://www.philholmes.net/lilypond/regtests/ - we're very > close to having a rating for all the tests. [...] "LilyPond Regression Test Rater Well - b

Re: regtests about very small differencies

Hi all, i've just got enlightened about this very old thread: On Tue, Sep 20, 2011 at 10:17 PM, Janek Warchoł wrote: > I want to fix an issue where a note is misplaced by about 0.07 > staffspace. I'll add a regtest for this, but how will we make sure > that it won't be

Re: regtests about very small differencies

On Mon, Jul 9, 2012 at 9:12 PM, Benkő Pál wrote: > hi Janek and all, > >> There's a much easier way: set staff-size to something really big. >> >> I suggest that we adopt this as an official policy: fixes for >> easy-to-overlook things should be documented by regtests using >> big/enormous font-si

Re: Texinfo help, please

On Wed, Jul 11, 2012 at 1:56 PM, David Kastrup wrote: > > "Phil Holmes" writes: > > It should wrap between the words "the file" and the filename. > > Obviously not enough stretchability for that to fit. You can try > > @tex > \global\emergencystretch=5in > @end tex > > and see where this gets yo

Re: GOP2: 2 - Stable releases and roadmap (radical change)

Hi All, Graham, first, let me apologise for not responding promptly. Secondly, here's my reply to Graham's almost-original proposition; i'll send a reply to current discussion ("Clear policy discussions") separately. On Tue, Jun 26, 2012 at 10:55 PM, Graham Percival wrote: > Let’s drop the “any

Re: GOP2: 2 - Stable releases and roadmap (radical change)

On Wed, Jul 11, 2012 at 6:07 PM, David Kastrup wrote: > Janek Warchoł writes: > >> What about something like this: >> when a regression against latest stable is found, it's not marked as >> critical (as Graham suggests). However, when we make a stable >> rele

Re: Regression test rater

On Wed, Jul 11, 2012 at 6:57 PM, Phil Holmes wrote: > This prompted me to check my indexing and it was mostly OK, but I found that > adding an index on RateUsername improves the speed of this query by a factor > of about 4. I think we're back to pretty much OK now. Yeah, previous delay was a bit

Re: regtests about very small differencies

On Mon, Jul 9, 2012 at 7:10 PM, Werner LEMBERG wrote: > >> I suggest that we adopt this as an official policy: fixes for >> easy-to-overlook things should be documented by regtests using >> big/enormous font-size (e.g. between 30 and 100, depending on >> issue). So, everyone checking regtests sho

Re: Texinfo help, please

On Wed, Jul 11, 2012 at 9:45 PM, David Kastrup wrote: > Graham Percival writes: >> Sure. So we're asking if TeX can be tweaked to consider >> additional solutions. (namely, "always add a line-break before >> anything with an overfull hbox, regardless of what that makes the >> rest of that parag

Re: Texinfo help, please

>From what i understand (based on David's description) the result in second case would rather be --- linewidth -- This is a paragraph which has a really long word and has benefitted from some kind of emergency-stretch-tweak which isn't IMO exactly what we

Re: GOP-PROP 2-1: LilyPond is part of GNU

Hi Graham (+1 for Graham!) & all (+1 for everybody!), let's try to summarize (can you update http://lilypond.org/~graham/gop/gop_2.html, Graham?) The numbers given are from GNU policies, see above. --required 6.3 - list authors check (git does this) 6.5 - copyright n

Re: GOP-PROP 2-1: LilyPond is part of GNU

On Thu, Jul 12, 2012 at 3:20 PM, David Kastrup wrote: > Janek Warchoł writes: > >> 3.4 - trigraphs in C code >> wtf? > > You can say that again. The following is valid C: > > ??=include > > int main(int ac, char *av??(??)) > ??< > prin

Re: web: Linux => GNU/Linux. English only. (issue 6374060)

On Thu, Jul 12, 2012 at 3:35 PM, wrote: > The change will appear with a "check-translation" when master will be > merged in translation, or a special "view" on Documentation/ in gitk. Cool! I didn't know that, thanks. Janek ___ lilypond-devel mailing

Re: clear policy discussions

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

Re: Meeting 2nd half of August!

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

Re: clear policy discussions

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

Re: Problem with uploading patch

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

Re: Meeting 2nd half of August!

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

Re: Problem with uploading patch

(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

Re: Problem with uploading patch

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

Re: clear policy discussions

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 tha

Re: Problem with uploading patch

Hi Harm, On Fri, Jul 13, 2012 at 11:38 PM, Thomas Morley wrote: > Hi Janek, > > UFF!! > > Thanks a lot. > Your hint about the wrong server was it. I overlooked it in the log > and I've absolutely no idea how it could happen that the server was > changed. Glad i helped! > BTW, > git config -e >

Re: clear policy discussions

On Sat, Jul 14, 2012 at 4:56 AM, Graham Percival wrote: > David, > > I realize that you are angry, but please stop using words like > "monkey" I'm responsible for "monkey". You asked to stop using it, but i continued to do so (not because of malice - i just didn't find good replacement). I apolo

Re: Stable 2.16 releases (dictator)

On Sat, Jul 14, 2012 at 6:15 AM, Graham Percival wrote: > Let’s appoint David Kastrup as the “benevolent dictator” of the > stable/2.16 git branch. +1 Janek ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/

Re: GOP2: 2 - Stable releases and roadmap (radical change)

On Sat, Jul 14, 2012 at 6:31 AM, Graham Percival wrote: > 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 >> &

Re: Stable 2.16 releases (dictator)

On Sat, Jul 14, 2012 at 11:30 AM, David Kastrup wrote: > "Trevor Daniels" writes: >> I suggest that you keep any such decision to yourself until >> just before the next stable is built, or defer making it until >> then. Otherwise interest in fixed such bugs will wane. > > And in the interest of

Re: GOP2: 2 - Stable releases and roadmap (radical change)

Hi, Keith, somehow i had overlooked this part of your email: On Wed, Jun 27, 2012 at 7:33 AM, Keith OHara wrote: > For any changed test then, it is probably worth reading the header, to > see if a subtle change that looks harmless happens to be the point of > the test (and would presumably cause

Re: Add function for overriding broken spanners to LilyPond. (issue 6397054)

On Wed, Jul 18, 2012 at 12:43 AM, wrote: > The function will override unbroken spanners, but it will ignore > non-spanners with a warning. What about things like clef change at a line break - is it possible to override them using this approach? It would be nice if i could, for example, paint a

Re: Problems with git (staging)

On Wed, Jul 18, 2012 at 11:35 AM, Marc Hohl wrote: > Hello list, > > I tried to follow the instructions on > http://lilypond.org/doc/v2.15/Documentation/contributor/working-with-remote-branches As Graham said, this is outdated and you don't need this. Everything that is necessary for basic pushi

Google tracker quota for attachments

Hi, for some time we've been "running low" on Google Tracker quota for attachments. Now i've read their documentation and the FAQ says "If you hit these limits, please contact us via our Google Group or email google-code-host...@googlegroups.com directly to discuss the situation." (http://code.goo

Re: GOP2-2b - Stable 2.16.x releases (dictator)

On Tue, Jul 17, 2012 at 7:32 AM, Graham Percival wrote: > 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. umm, shall i declare my support once again? ;) For the archive's sake: that's a +1! J

Re: Syntax change proposal:

On Mon, Jul 16, 2012 at 10:18 AM, David Kastrup wrote: > The key point is being able to employ user-definable functions in a wide > variety of situations. We currently have the situation that > [...] Whoah, that was one hell of an explanation. I think i understood it (at least most parts) and i

Re: Add function for overriding broken spanners to LilyPond. (issue 6397054)

On Wed, Jul 18, 2012 at 1:56 PM, David Nalesnik wrote: > Perhaps this is a candidate for a different function, > and possibly the name \alterBroken should be changed to something more > precise? (I thought \alterBrokenSpanner or \overrideBrokenSpanner would be > an awful lot to type.) I prefer s

Re: Add function for overriding broken spanners to LilyPond. (issue 6397054)

On Wed, Jul 18, 2012 at 8:18 PM, Thomas Morley wrote: > 2012/7/18 Janek Warchoł : >> I haven't seen it before - looks awesome :) >> (however, it would be even more awesome if it was one general function >> for all purposes ;) ) > > I wrote this snippet a year ago.

Re: Add function for overriding broken spanners to LilyPond. (issue 6397054)

On Thu, Jul 19, 2012 at 2:17 AM, David Nalesnik wrote: > I took a look at this--I couldn't resist!!--and actually it wasn't too hard > to incorporate Harm's (very cool) snippet into \alterBroken. I've attached > a file which shows how his example would be expressed with that command. :D > I rea

Re: Web: remove non-Free software from Easier Editing (issue 6395049)

On Thu, Jul 19, 2012 at 9:43 AM, wrote: > It's OK as it is, but why the commented out text that refers to non-free > software cannot be deleted? If it's because we want to be able to find > a reference by looking at the source, Git history will tell. +1

  1   2   3   4   5   6   7   8   9   10   >