Re: [testlilyissues:issues] Ticket 3960 discussion

James wrote: Wednesday, October 18, 2017 11:54 AM >- **status**: Started --> Invalid > - **Patch**: needs_work --> > - **Comment**: > > Revisiting this, the example given at the start of this issue > > http://lilypond.org/doc/v2.18/Documentation/notation/explicit-breaks > > has no

Re: Introduction + how/what to contribute?

"Koen Samyn" wrote Thursday, September 28, 2017 9:02 AM Hi and Welcome! > I am trying to get started with the lilypond source code and see where I > can contribute, but the documentation links seem out of order, for example > the following link: > >

Re: How to locate all layout-property values for a particularLayoutObject in the source files?

Simon Albrecht wrote Sunday, September 24, 2017 4:34 PM > On 24.09.2017 14:30, James wrote: >> Where would I go to see the 'complete list' of all possible NoteHead.style >> values > > > > – the description

Re: PATCHES - Countdown for September 10th

James wrote Tuesday, September 12, 2017 9:05 AM > On Mon, 11 Sep 2017 23:24:31 +0200 > Thomas Morley wrote: > >> for about a month I'm often surprised about new issues/patches etc. >> I _am_ subscribed to the lilypond-auto mailing-list which should >> notify me about

Re: Issue 5187 Add command for Thin Aiken noteheads (issue 326510043by karlinh...@gmail.com)

Karlin High Wednesday, September 20, 2017 6:46 PM > On Wed, Sep 20, 2017 at 12:37 PM, wrote: >> This is my first effort at making a patch, so I could be doing things wrong. > > I gather I am supposed to request write access to the issue tracker on > Sourceforge?

Re: PATCHES - Countdown for September 10th

James wrote Tuesday, September 12, 2017 9:05 AM > If you look here: > > http://lists.gnu.org/archive/html/lilypond-auto/ > > It seems that the emails stopped 2nd August. > > I wonder if there is some 'spam' setting that has been triggered on the > lilypond-auto list? I can't see anything

Re: Propose Commit access for Étienne Beaulé

James wrote Thursday, September 07, 2017 4:19 PM > Étienne has pushed couple of patches now and I wondered if we could > perhaps give him full commit access to git? Who now has the authority to do this? I don't, and I've lost track of who does now that Han-Wen, Jan and Graham are rarely seen

Re: Issues write access

Étienne Beaulé wrote Thursday, August 10, 2017 2:51 AM > Hello. May I be granted write access on our issue tracker? My username is > ebe123. Thank you! Added. Welcome! Trevor --- This email has been checked for viruses by AVG. http://www.avg.com

Re: Any objections to branching off a stable branch for 2.20?

Phil Holmes wrote Tuesday, July 18, 2017 11:07 AM > Subject: Any objections to branching off a stable branch for 2.20? > No objections from me towards aiming for a 2.20 stable release. None from me either. Trevor --- This email has been checked for viruses by AVG. http://www.avg.com

Re: Releasing 2.20

David Kastrup wrote Wednesday, June 07, 2017 9:34 PM > tomorrow I am leaving for physical therapy. Hope it all goes well for you. > So I should be able to do some reasonably straightforward work. Good, but that should not be your priority ATM. > So how is it going to end up? Barring

Re: Back in the Pond

Hi David Thanks for the update. You wrote Monday, May 29, 2017 9:56 PM > Gianmaria Lari writes: >> >> what's the better way to give a financial contribution? > > In Europe's EURO zone (guessing from your name, that would likely be the > case) SEPA transfers are

Re: Merge Rests Engraver

Jay Anderson wrote Wednesday, May 17, 2017 7:31 AM > Thanks. When I ran `git cl upload origin/master` it wasn't able to associate > the patch with an issue: > We were not able to associate this patch with a tracker issue. > Please enter a valid tracker issue number > (or enter nothing to

Re: Calling in for sickness

David, you wrote Monday, May 15, 2017 5:42 PM > had a sort of apoplexy and will not be able to do anything while > recovering. I am hospitalized at the moment, CRT and MRT did not show > any specific anomalies but my right side is hampered and I cannot yet > swallow or cough which is sort of

Re: Merge Rests Engraver

Hi Jay, you wrote Sunday, May 14, 2017 5:15 AM > When running git-cl it failed to create a new ticket number to track the > issue (the instructions say I need to request access: > http://lilypond.org/doc/v2.19/Documentation/contributor/git_002dcl#configuring-git_002dcl). > There is an existing

Re: 2.19.59: Bad horizontal spacing when \override LyricText #'X-offset

Dmytro O. Redchuk wrote Friday, April 28, 2017 9:10 AM > please take a look at this MWE: > % --- 8< \version "2.19.59" { r4 a a2 a4 a2 } \addlyrics { \override LyricText #'X-offset = #0 "Блаженні голодні й спрагнені правди, бо вони на" -- си -- тять -- ся. } % --- 8<

Re: Add a \voicify command (issue 320820043 by d...@gnu.org)

David Kastrup wrote Sunday, April 09, 2017 5:14 PM > > Harm brought a few points, one concerning different warning/error > behavior (and with regard to the _text_ of the existing warning, I will > cede the point thought there isn't yet a proposal for \voices as far as > I can see). He also

Re: Add a \voicify command (issue 320820043 by d...@gnu.org)

David Kastrup wrote Friday, April 07, 2017 9:07 PM > "Trevor Daniels" <t.dani...@treda.co.uk> writes: > >> David, you wrote Thursday, April 06, 2017 4:54 PM >> >>> You could try separate commands \voicifyUp and \voicifyDown . I am not >>>

Re: Add a \voicify command (issue 320820043 by d...@gnu.org)

David, you wrote Thursday, April 06, 2017 4:54 PM > You could try separate commands \voicifyUp and \voicifyDown . I am not > sure whether or not \voicify should not be \voices or \voicing or > \voicings instead, possibly making for nicer compounds like that. > > I mean, something like > >

Re: Lily version operators documentation

Urs Liska wrote Wednesday, February 15, 2017 8:04 AM > Am 14.02.2017 um 18:27 schrieb Trevor Daniels: > >> As these functions are not intended for the usual LilyPond user I >> don't think the NR is suitable, other than to have them listed in A22. >> Similarly, they will

Re: Lily version operators documentation

Urs Liska wrote Tuesday, February 14, 2017 9:23 AM > my patch https://sourceforge.net/p/testlilyissues/issues/5067/ > http://codereview.appspot.com/317270043 is currently on countdown. It > introduces the procedures > > - lilypond>? > - lilypond>=? > - lilypond - lilypond<=? > - lilypond=? > >

Re: request for LilyPond issue tracker user account

Flaming Hakama by Elaine wrote Wednesday, February 08, 2017 9:12 PM >I endeavored to start contributing to lilypond development. Great! > I've been following the steps in the contributor docs, and on the git-cl > page instructs me: > >

Re: Issue 3830: Document \offset command (issue 319150043 bydavid.nales...@gmail.com)

david.nales...@gmail.com wrote Tuesday, January 24, 2017 10:57 PM > Question: > > How do I get a backslash in @subsubsubheading{} ? > > The literal symbol doesn't show up, and @backslashchar{} displays > @backslashchar{} >From memory it's @bs{}. Trevor

Re: Back in the Pond

David, you wrote Thursday, January 19, 2017 10:18 AM > it would appear that my excursion into a regular workplace ended up somewhat shortlived. Really sorry to hear that, but it's great to have you back! > So for the short time range, I am again dependent > on support by other LilyPond

Re: How to adjust space between ChordNames and Staff?

Thomas Morley wrote Friday, January 13, 2017 9:05 PM > 2017-01-13 17:05 GMT+01:00 Trevor Daniels <t.dani...@treda.co.uk>: >> >> Risto Vääräniemi wrote Friday, January 13, 2017 3:15 PM >> >>> On 13 January 2017 at 01:20, Trevor Daniels <t.dani...@treda.co

Re: How to adjust space between ChordNames and Staff?

Risto Vääräniemi wrote Friday, January 13, 2017 3:15 PM > On 13 January 2017 at 01:20, Trevor Daniels <t.dani...@treda.co.uk> wrote: > >> Thomas Morley wrote Thursday, January 12, 2017 10:26 PM >> >>> 2017-01-12 21:13 GMT+01:00 Risto Vääräniemi <risva...@gmai

Re: How to adjust space between ChordNames and Staff?

Thomas Morley wrote Thursday, January 12, 2017 10:26 PM > 2017-01-12 21:13 GMT+01:00 Risto Vääräniemi : > >> The spacing between ChordNames and Staff seems a bit tight by default. I've >> been trying to adjust it but I haven't figured out the right magic words > > Do it in

Re: Staging Broken with last makelsr - incorrect TexInfo commandformat

David Nalesnik wrote Wednesday, January 11, 2017 3:22 PM > Ok, so I will probably do > > git revert HEAD > > in my staging branch > > and push it to origin/staging. > > --- > > I won't attempt to clear the LSR queue in preparation for my patch > update (as I did) by running makelsr.py

Re: adding a snippet to a patch

David Nalesnik wrote Monday, January 09, 2017 9:51 PM > On Mon, Jan 9, 2017 at 2:00 PM, David Nalesnik > wrote: > >> I'm adding a snippet to a patch dealing with hairpins, and I'm not >> sure what I need to do. >> >> I've added the snippet to

Re: 5027: NR example with bad engraving practice

Simon Albrecht wrote Thursday, January 05, 2017 10:16 PM >>> On 04.01.2017 15:01, Hans Åberg wrote: This is just a quirk of the 4/4 [meter], also mentioned in Hindemith, "Elementary Training", p. 30. In other words, the note should not cross the 2nd and 4th metric accents, but

Re: LilyPond 2.20 release process

Phil Holmes wrote Saturday, December 31, 2016 11:03 AM >I think there are a few bugs that need attention prior to stable release. > https://sourceforge.net/p/testlilyissues/issues/4975/ is one I'm aware of, > and there are a number of ones marked as critical. There are four bugs marked as

Re: Delete new LSR-snippet?

Knut Petersen wrote Friday, December 23, 2016 11:53 PM Harm, would this be a better snippet for the LSR? >> I seem to remember a post or maybe an LSR entry for placing >> divisi arrows at the end of a staff. Maybe this could be >> adapted to achieve the same effect more reliably? >> >> Found

Re: [PATCH [uploaded to Rietveld]] Automatic lyric extenders

Alexander Kobel wrote Monday, December 26, 2016 1:00 AM > Oh well, it's late. I didn't spot measure 7, with the 8( 8) in alto. > Same there. > And, of course, you should have an extender there in the second verse, > and you should have extenders in measure 1 (was/was/shall) an measure 9 >

Re: [PATCH [uploaded to Rietveld]] Automatic lyric extenders

Alexander Kobel wrote Sunday, December 25, 2016 2:19 PM > But: I cannot imagine a situation where I would not use automatic > extenders, so I'm a really bad person to judge the need and requirements > for a manual mode. One obvious and fairly common situation is when there are several verses

Re: Delete new LSR-snippet?

Thomas Morley wrote Friday, December 23, 2016 11:42 AM > with > http://lsr.di.unimi.it/LSR/Item?u=1=1049 > a new snippet arrived. > Though, it only demonstrates how to use 'extra-offset, imho. > I tend to delete it, otoh I don't want to scare away a possible new > contributor... > > Opinions?

Re: [PATCH] Automatic lyric extenders

Knut Petersen wrote Thursday, December 22, 2016 12:33 AM > Attached find a new version of the patch. > Please test. Read the updated manuals. > > Feel free to provide corrections and translations! Looks promising. I have several comments to make, but it will be much easier to do that when the

Re: music function to be included somewhere in scm/*

Noeck wrote Friday, December 16, 2016 9:08 PM > Am 16.12.2016 um 17:38 schrieb Alexander Kobel: >> [2] Side Note: other proposed names for minimum-length so far: >> >> (1) minimum-space >> (2) show-length >> (3) hide-below-length >> (4) hide-if-shorter-than >> (5) minimum-visibility >> (6)

Re: music function to be included somewhere in scm/*

Knut Petersen wrote Thursday, December 15, 2016 6:08 PM >> Another common use case occurs when the lyrics in several verses have >> melismata in different places. This is usually indicated with dashed slurs, >> occasionally even with two such slurs starting on the same note. When >> there are

Re: music function to be included somewhere in scm/*

Alexander Kobel and Knut Petersen wrote Thursday, December 15, 2016 4:45 PM OK, thanks for your explanations. Clearly the patch is an improvement for this use case: > On 2016-12-15 17:19, Trevor Daniels wrote: > > Currently, I set minimum-length = 0 in all Lyric contexts so that I &g

Re: add choral and choral-cautionary accidental style (issue311430043by perpeduumimmob...@gmail.com)

Alexander, you wrote Thursday, December 15, 2016 3:51 PM > On 2016-12-15 13:34, Trevor Daniels wrote: > >> Adding you to the dev list is very little work, but you do have to >> get a SourceForge id and tell me what it is for me to do that. >> >> James probably is

Re: music function to be included somewhere in scm/*

Knut Petersen wrote Thursday, December 15, 2016 1:55 PM > minimum-length in my patch means: > - Don't generated automatic extenders if it's impossible to give them > minimum-length. > - Use minimum-length for forced extenders at unusual places (single note) if > possible. > > I think the most

Re: add choral and choral-cautionary accidental style (issue311430043by perpeduumimmob...@gmail.com)

own to Allura you will not be able to contribute to any discussion on _any_ issue - including those James has created on your behalf. Trevor > On 2016-12-14 16:28, Trevor Daniels wrote: >> >> Alexander, you wrote Wednesday, December 14, 2016 12:32 PM >> >>> On 2016-12-1

Re: add choral and choral-cautionary accidental style (issue311430043 by perpeduumimmob...@gmail.com)

Alexander, you wrote Wednesday, December 14, 2016 12:32 PM > On 2016-12-14 13:15, James wrote: > >> On 13/12/16 20:10, perpeduumimmob...@gmail.com wrote: >>> Reviewers: , >>> >>> Message: >>> add choral and choral-cautionary accidental style >> ... >>> >>> Please review this at

Re: Stepping down and moving on

David, you wrote Wednesday, November 09, 2016 5:09 PM > I have accepted a full-time development (and team management) position > with another company. Due to their project and team expansion plans, > I will be starting already in December. I sincerely hope you're finding your new job engaging

Re: Lilypond python upgrade

Andrew Bernard wrote Thursday, December 08, 2016 1:28 AM > Moving a thread across from the user list, I just wanted to let people know > that I will be starting on the work of upgrading lilypond to use Python 3 - > yes, with all the complexity that entails. I am happy to have a serious > shot

Re: bypassing the patch countdown

Graham Percival wrote Wednesday, December 07, 2016 10:34 PM > We instituted the policy of patch countdowns and Patchy after the > lengthy wait for 2.14.0, which was due to a large number of > regression bugs due to patches which either broke the compile, or > broke previously-working output. >

Re: Stepping up, contributor mentoring

- Original Message - From: "Trevor Daniels" <t.dani...@treda.co.uk> To: "Graham Percival" <gra...@percival-music.ca> Cc: <lilypond-devel@gnu.org> Sent: Friday, December 02, 2016 7:59 PM Subject: Re: Stepping up, contributor mentoring > > Gra

Re: Stepping up, contributor mentoring

Graham you wrote Friday, December 02, 2016 6:34 PM > On Tue, Nov 29, 2016 at 11:37:04PM -0000, Trevor Daniels wrote: >> >> Graham Percival wrote Tuesday, November 29, 2016 11:11 PM >> >> > So, are there any vacancies on the Bug Squad? I've signed up for >&g

Re: Stepping up, contributor mentoring

Graham Percival wrote Tuesday, November 29, 2016 11:11 PM > Hi all, I'm back. Great! Welcome back! We've missed you! > So, are there any vacancies on the Bug Squad? I've signed up for > sourceforge (username: gperciva). I've added you to SF as a Developer (gives you Read, Create, Update

Re: Stepping down and moving on

Hi David The first thing to do is to sincerely thank you for your extreme dedication, skill and energy in developing our favourite program over recent years. Even that seems a weak effort at expressing the gratitude and admiration I feel. We owe you a great deal. But eventually we all have

Re: issue tracker access

Hi Janek > can you give me write access to the sourceforge issue tracker? My > sourceforge username is janek-warchol. Done. Added as Developer (Read/Create/Update Issues). Welcome back! Trevor ___ lilypond-devel mailing list

Re: change title of doc-tagged lsr-snippet 586

Thomas Morley wrote Sunday, October 09, 2016 11:20 PM >2016-10-10 0:07 GMT+02:00 Trevor Daniels <t.dani...@treda.co.uk>: >> >> Thomas Morley wrote Sunday, October 09, 2016 8:46 PM >> >>> in /Documentation/snippets we have markup-lines.ly coming from LSR. &g

Re: Help with Scheme engraver please

Trevor Daniels wrote Saturday, September 17, 2016 9:57 PM > Thomas Morley wrote Friday, September 09, 2016 11:31 PM > >> 2016-09-08 0:07 GMT+02:00 Trevor Daniels <t.dani...@treda.co.uk>: >>> >>> But I don't understand why you >>> used a rather comp

Re: Help with Scheme engraver please

Thomas Morley wrote Friday, September 09, 2016 11:31 PM Hi Harm back now from my week away ... > 2016-09-08 0:07 GMT+02:00 Trevor Daniels <t.dani...@treda.co.uk>: >> >> But I don't understand why you >> used a rather complicated procedure to obtain durations. Coul

Re: Help with Scheme engraver please

- Original Message - From: "Thomas Morley" <thomasmorle...@gmail.com> To: "Trevor Daniels" <t.dani...@treda.co.uk> Cc: "Lily-Devel List" <lilypond-devel@gnu.org> Sent: Sunday, September 04, 2016 7:28 AM Subject: Re: Help with Scheme engra

Re: Help with Scheme engraver please

Thomas Morley wrote Friday, September 02, 2016 8:22 PM > 2016-09-02 13:05 GMT+02:00 Trevor Daniels <t.dani...@treda.co.uk>: >> >> There already is a helpful working example in the code base. See >> >> input/regression/scheme-engraver.ly >> >> Thi

Re: Help with Scheme engraver please

Simon, you wrote Friday, September 02, 2016 1:34 AM Hi Simon, >On 24.08.2016 11:51, Trevor Daniels wrote: >> David Kastrup wrote Wednesday, August 24, 2016 7:48 AM >>> "Trevor Daniels"<t.dani...@treda.co.uk> writes: >>>> Prompted by the recen

Re: Help with Scheme engraver please

David Kastrup wrote Wednesday, August 24, 2016 7:48 AM > "Trevor Daniels" <t.dani...@treda.co.uk> writes: > >> Prompted by the recent discussion on lute tablature, I tried coding a >> Scheme engraver to create the duration grobs but quickly ran into a >>

Help with Scheme engraver please

Prompted by the recent discussion on lute tablature, I tried coding a Scheme engraver to create the duration grobs but quickly ran into a problem. I need to collect information from both a Listener and an Acknowledger so the obvious place to build the grob is in stop-translator-timestep, but

Re: repeating bar numbers and rehearsal marks in frenched score

Mark, you wrote Monday, August 01, 2016 6:03 PM > At 14:21 on 01 Aug 2016, Phil Holmes wrote: > >>If you create an account on SourceForge and let us have the details, >>I'll add you to the tracker users. > > username: mkdev > email: m...@opus11.net You're now a developer AFA SourceForge is

Re: GSoC spanners review/update

Nathan, you wrote Tuesday, July 19, 2016 10:03 PM > Can you please add my account starrynte (email address is > starry...@gmail.com)? You're now a developer AFA SourceForge is concerned, which means you can add Issues. There are a few more hoops to jump through before you can submit

Re: GSoC spanners review/update

Nathan Chou wrote Tuesday, July 19, 2016 10:26 AM > I have (except for one question below) finished adapting > Dynamic_engraver and Dynamic_align_engraver to work cross-voice. I > plan to continue with other spanners (perhaps slurs next), but I want > to make sure I am on the right track. I

Re: Patch

Steven, you wrote Friday, May 27, 2016 9:22 PM >>Thomas Morley wrote Friday, May 27, 2016 3:07 PM >> >>> 2016-05-27 6:11 GMT+02:00 Steven Weber : Since I don't have an official mentor and the recommendation is that you send your first couple of patches to your

Re: Patch

Hi Steven Thomas Morley wrote Friday, May 27, 2016 3:07 PM > 2016-05-27 6:11 GMT+02:00 Steven Weber : >> >> Since I don't have an official mentor and the recommendation is that you >> send your first couple of patches to your mentor first, I thought I'd send >> it to the

Re: No countdown today

David Kastrup wrote Saturday, May 14, 2016 9:19 AM > James writes: > >> It seems that there is some intermittent issue at Savannah.gnu.org >> that is stopping me from pulling or fetching (I am getting either >> 'SSH-message' errors or 'fatal read' errors. >> > I got it mostly

Re: Rewriting the Translator definition framework

David Kastrup wrote Friday, April 22, 2016 1:07 PM > I am currently doing pitch 2 at first-class Scheme engravers and am > sorely tempted to scratch the whole macro-based mess and do it via > inheritance and templates. > > Now the sore point is that the basic type for which Scheme functions are

Re: Lilypond issue tracker account request

Karl O. Pinc wrote Tuesday, March 22, 2016 2:32 PM > On Tue, 22 Mar 2016 12:14:37 - > > "Trevor Daniels" <t.dani...@treda.co.uk> wrote: > >> Karl O. Pinc wrote Tuesday, March 22, 2016 3:47 AM > >> > I'd like an account in the lilypond issue t

Re: Lilypond issue tracker account request

Karl O. Pinc wrote Tuesday, March 22, 2016 3:47 AM Hi Karl > I'd like an account in the lilypond issue tracker. Happy to add you to the Issue Tracker as a Member. That allows you to comment on Issues without moderation. That's the way to start. You'll need to post or send me your SourceForge

Re: What to do with snippet "Centering markup on note headsautomatically"?

Thomas Morley wrote Saturday, March 12, 2016 12:20 PM > http://lists.gnu.org/archive/html/lilypond-user/2016-03/msg00302.html > states correctly that the LSR-snippet "Centering markup on note heads > automatically" > http://lsr.di.unimi.it/LSR/Item?id=637 > doesn't work in 2.19.x anymore. > It's

Re: Unable to use git-cl

Carl, you wrote Tuesday, March 08, 2016 6:54 PM > > I can upload patches to Rietveld, as you can see at > > https://codereview.appspot.com/283550043 > > but the links to the issue tracker never get made. > > As far as I can see, we have a custom git-cl, so I can't get general help > anywhere

Re: Verifying issues

Simon Albrecht wrote Wednesday, March 02, 2016 10:52 PM > I noticed that there have been many ‘Issues to verify’ around, so I > started to catch up with these. Now the question is: Shouldn’t we only > mark issues as verified, when the change is already included in an > official release? Yes,

Re: Commit access

Paul Morris wrote Monday, February 29, 2016 1:57 AM > In issue 4776 James wrote: > >> @Paul, you may want to apply for commit access yourself if you like as I >> think you've done enough work for the 'cause' to > > So I’d like to request commit access. Among other things this will save >

Re: Allura account

Hi Valentin Nice to have you back! I've added your username as a Developer, so you should now be able to Read, Create and Update Issues. Trevor - Original Message From: "Valentin Villenave" <valen...@villenave.net> To: "Trevor Daniels" <t.dani...@tr

Re: Allura account

Hi Carl > My user name is cds4byu I see you're already registered as a Developer on Allura. Maybe Phil just beat me to it. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: text-replacements: add and the like (issue 281470043 bysimon.albre...@mail.de)

Simon Albrecht wrote Monday, January 25, 2016 8:03 PM > How should I (and James) interpret the silence here? Any more opinions? If a user has requested additional characters which have an html character (non-numeric) definition and a developer is willing to do the work I see no reason why

Re: Add RemoveEmptyStavesAll command (issue 283050043 bysimon.albre...@mail.de)

Simon Albrecht wrote Thursday, January 14, 2016 3:34 PM > On 14.01.2016 16:20, d...@gnu.org wrote: >> The name is rather clumsy (and it does not help that the issue report >> talks about "\RemoveEmptyStavesFirst" while the actual patch and the >> Rietveld review has "\RemoveEmptyStavesAll"). >>

Re: Request for developer status on the issue tracker

Heikki Tauriainen wrote Friday, January 08, 2016 1:04 PM > I understand that running git-cl to create new issues requires > developer status on the issue tracker at Sourceforge. I've just > created a SourceForge account, and would kindly request developer > access to the issue tracker (if

Re: Request for developer status on the issue tracker

Heikki, you wrote Friday, January 08, 2016 4:18 PM > I still managed (like I always seem to do when I run git-cl with > several months having passed since the last time...) to fail to submit > a patch with git-cl fully successfully (*), so I had to create a new > issue for the tracker

Re: Error in git-cl creating a new issue

John Gourlay, you wrote Wednesday, January 06, 2016 3:07 AM >I just submitted a small change to the Contributors Guide using git-cl. The >patch got into codereview.appspot.com, but not into >sourceforge.net/p/testlilyissues/issues/. I let git-cl create a new issue for >the patch, but it

Re: Error in git-cl creating a new issue

Simon Albrecht, you wrote Wednesday, January 06, 2016 1:14 PM > On 06.01.2016 13:26, Trevor Daniels wrote: >> John Gourlay, you wrote Wednesday, January 06, 2016 3:07 AM >> >> >>> I just submitted a small change to the Contributors Guide us

Re: Error in git-cl creating a new issue

Simon, you wrote Wednesday, January 06, 2016 4:05 PM > The rietveld part is fine. Only the Allura part reliably fails, with the > same kind of messages that John reported. > I’ve just been creating issues manually. Well, a 403 HTTP error means the server received and understood the request but

Re: lilypond-auto doesn't work correctly

Werner, you wrote Tuesday, December 22, 2015 4:11 AM > Is it possible to resurrect correct functionality of the > `lilypond-auto' list? Currently, no mails from allura are sent to > it, which makes it sort of useless... There is a comparable list, Testlilyissues-auto, at SourceForge. I've

Re: Musicians prefer LilyPond scores, study finds

Francisco Vila wrote Thursday, December 17, 2015 4:53 PM > I just gained my PhD. My humble thesis tells the design and results of > an experiment with a number of musicians, comparing lilypond scores > with the originals which those scores were copied from. Congratulations Dr Vila! As your

Re: On issues that are marked as 'Patch_Abandoned'

evel" <lilypond-devel@gnu.org> Cc: "Trevor Daniels" <t.dani...@treda.co.uk>; "David Kastrup" <d...@gnu.org>; "simon Albrecht" <simon.albre...@mail.de> Sent: Saturday, November 21, 2015 7:14 PM Subject: On issues that are marked as 'Pa

Re: SubdivideBeam gives undesired result when beaming over more thana quarter note

Urs Liska wrote Thursday, November 19, 2015 11:20 PM > However, I have a question: Where are the CLI messages defined that are > used in the git-cl process? This is still talking about Google issue > tracker items. Good point. That was why I thought you might not have updated git-cl. Copying

Re: Allura account

Hi Urs This isn't documented as the expectation was that this was a brief temporary home for the issues DB while a new permanent home at Savannah was brought into service. But it seems that has stalled, so maybe we ought to rethink this and document the present position. Anyway, all you need

Re: Allura account

Oh, and you also need to pull the latest version of git-cl. Trevor - Original Message - From: "Trevor Daniels" <t.dani...@treda.co.uk> To: "Urs Liska" <u...@openlilylib.org> Cc: "Lily-Devel List" <lilypond-devel@gnu.org> Sent: Thursda

Keeping the list of issues in active development current

Devs and Bug Squad The list of issues obtained by clicking Open (Begun) in Allura now contains just those issues that were Started within the last 6 months or have a currently active Owner. Those that don't have a currently active Owner should be reverted to Status:Accepted when they have

Tidying-up the Issues DB

Devs, Bug Squad: Many of the Issues with Status:Started are no longer active, with many not seeing any change for several years. Following the move of the Issues DB from GC to SF many of the original owners of these Started Issues have not re-registered at SF; indeed many are no longer active

Re: Allure and git-cl troubleshooting

Hi Paul Looking at the error again it seems to be a problem with authenticating at GoogleCode rather than Allura at SourceForge. Trevor - Original Message - From: "Paul Morris" <p...@paulwmorris.com> To: "James" <p...@gnu.org> Cc: "Phil Holmes&qu

Re: Tidying-up the Issues DB

James wrote Monday, October 26, 2015 11:54 AM > On 26/10/15 11:29, Trevor Daniels wrote: >> Devs, Bug Squad: >> >> Many of the Issues with Status:Started are no longer active, with many not >> seeing any change for several years. Following the move of the Issue

Re: Allure and git-cl troubleshooting

Paul Morris wrote Sunday, October 25, 2015 9:33 PM > I gave git-cl another try and got the same error from my previous message, > ending in: > > File "/usr/lib/python2.7/urllib2.py", line 558, in http_error_default > raise HTTPError(req.get_full_url(), code, msg, hdrs, fp) >

Re: Allure and git-cl troubleshooting

Paul Morris wrote Sunday, October 25, 2015 7:48 PM > Below is an error I got trying to upload with git-cl, the new Allura version > that’s in LilyDev4. I followed James and Phil’s recent email exchange about > how to do config with Allura server url, source forge account, bearer token, >

Re: Allure and git-cl troubleshooting

Paul, you wrote Sunday, October 25, 2015 8:45 PM >> On Oct 25, 2015, at 4:32 PM, Trevor Daniels <t.dani...@treda.co.uk> wrote: >> >> Maybe not the cause of this particular problem, but only authenticated >> developers are permitted to edit tickets, which is what g

Re: StaffPad

Urs Liska wrote Thursday, October 08, 2015 10:34 AM > Am 08.10.2015 um 11:32 schrieb Werner LEMBERG: > >> I was quite impressed seeing the following video. >> >> https://www.facebook.com/verge/videos/975966512439692/ >> >> If writing music like this *really* works, I could imagine that even I

Fw: [forge:site-support] #11271 Discussion posts vanish if a ticket's title is edited

*: > > Greetings, > Our engineering team has indicated this issue has been resovled. > Thanks > SourceForge Support > > > > --- > > ** [site-support:#11271] Discussion posts vanish if a ticket's title is > edited** > > **Status:** fixed > **L

Re: Google-to-Allura port adds brackets around rests

- Original Message - From: "Trevor Daniels" <tr...@treda.co.uk> To: "Trevor Daniels" <t.dani...@treda.co.uk>; "Lily-Devel List" <lilypond-devel@gnu.org>; "Simon Albrecht" <simon.albre...@mail.de> Sent: Tuesday, September 08

Re: Allura task list

Trevor Daniels wrote Friday, September 18, 2015 9:14 PM > > Dan Eble wrote Tuesday, September 15, 2015 2:08 AM > >> It would be convenient to have a search button that finds issues assigned to >> the logged-in developer which are not yet fixed. Is that possible? > &

Re: Allura task list

Dan Eble wrote Monday, September 28, 2015 10:37 PM > On Sep 28, 2015, at 11:27 , Trevor Daniels <t.dani...@treda.co.uk> wrote: >> >> Trevor Daniels wrote Friday, September 18, 2015 9:14 PM >> >>> Dan Eble wrote Tuesday, September 15, 2015 2:08 AM >

Re: List of Issues with 'patch_abandoned' assigned to them - as ofSeptember 2015

David Kastrup wrote Sunday, September 20, 2015 11:34 PM > James Lowe writes: > >> On 20/09/15 22:52, Simon Albrecht wrote: >>> On 20.09.2015 23:10, James Lowe wrote: My thinking is like this; I pick an issue to work on, I do some stuff, make a patch, have a

Tracking Issue activity on Allura at SF

Devs and Bug Squad: If you haven't yet signed up to Allura at SourceForge you may be missing discussions on Issues and finding it difficult to keep up with changes to the Issues DB (there are already around 40 new issues and many more comments and changes since we moved from GC a month ago).

  1   2   3   4   5   6   7   8   9   10   >