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

complication is that R1 has been converted into [r1]… I don't understand what the url links in GC were supposed to do, but whatever it was they are broken now. I've never seen links attached to rests before, so I think this is a one-off, probably caused

Re: sourceforge-problem

/ > opposed to changing owner, which worked. > > Are permissions different/restricted? No. I have another ID which is dev (rather than admin) and I can change it. Are you clicking on the edit right at the top of the issue, on the same line at the title? Trevor

Re: Allura API

" and finds their Rietveld URLs. The theory works just >> as well with patch:new, but there were so few results it didn't >> demonstrate much. >> >> http://philholmes.net/lilypond/allura/ > > Been doing other things recently, but this link is now update

Implementing Blocking in Allura

know of any others please tell me. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: PATCHES: Countdown for September 8th 2015

Thomas Morley wrote Saturday, September 05, 2015 10:32 AM > I created an account at SF. > User-name: thomas-morley Added as dev > Currently I cannot change owner of 4575 > Iirc, I need to be registered as a dev? Yes; should be ok n

Re: PATCHES: Countdown for September 8th 2015

eceive those emails, as some progress is being made with Allura at Savannah. Let's wait another week before suggesting all devs register in the hope we can migrate to Savannah soon. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Small error in Allura issue import

Simon Albrecht wrote Friday, September 04, 2015 11:08 PM > > Am 04.09.2015 um 13:17 schrieb Trevor Daniels: >> Simon Albrecht wrote Friday, September 04, 2015 12:50 AM >> >>> I won’t fix this now, because we have no solution for the problem that >>> all comm

Re: Small error in Allura issue import

ts re-appeared! We need to try to understand what is happening here. @Simon: could you try doing that to see if it resurrects the comments of our real issue 3900. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Small error in Allura issue import

o moderation would not have been involved. I've just tried editing the title in my other "testlily" project and it works fine when reinserting the <> in plain text. None of the comments were deleted. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: thinking twice about the new issue tracker

Federico Bruni wrote Thursday, September 03, 2015 10:21 AM > > Il giorno gio 3 set 2015 alle 11:03, Trevor Daniels > ha scritto: >> >>> It works quite well. Status and labels are migrated correctly. >>> Attachments are saved on Github server and displayed inl

Re: thinking twice about the new issue tracker

e/lilyissues/issues/4551 https://github.com/fedelibre/lilyissues/issues/4548 https://github.com/fedelibre/lilyissues/issues/4491 seem to have broken links rather than images. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu

Re: thinking twice about the new issue tracker

ld get > more than marginal interest of the FSF if we got it working for us. The kallithea issue tracker appears to be at bitbucket: https://bitbucket.org/conservancy/kallithea/issues They don't seem to have one of their own. Trevor ___ lilypon

Re: thinking twice about the new issue tracker

f. It is only through advertising that all the free (as in no charge) services we enjoy are available to us. The advertisers pick up all the bills for hosting and connection charges. Seems a fair-enough deal to me. It's easy to ignore the adverts. Trevor ___

Re: thinking twice about the new issue tracker

David Kastrup wrote Wednesday, September 02, 2015 11:46 AM > "Trevor Daniels" writes: > >> And we'd be limited to 5 developers, unless we pay, it seems. >> Hardly opensource. > > More like "hardly gratis". I've just glanced cursorily at

Re: thinking twice about the new issue tracker

Federico Bruni wrote Wednesday, September 02, 2015 10:27 AM > > Il giorno mer 2 set 2015 alle 11:11, Trevor Daniels > ha scritto: > >>> meanwhile we use Bitbucket or Github? Not Free services, I know, but at >>> least their business model seems honest. >&g

Re: thinking twice about the new issue tracker

ve our DB with 4000-odd records can be imported from GC to GitHub by doing it. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: thinking twice about the new issue tracker

y of moving the DB to somewhere where it could continue to be updated without hiatus. I seemed to be the only one who thought this important. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: thinking twice about the new issue tracker

that can be exported > by the tool, per repo. > If your project has more than 1,000 issues the export will fail. We have over 4,000. With image attachments. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allura at SF is ready

Federico Bruni wrote Wednesday, September 02, 2015 4:29 AM > Il giorno dom 30 ago 2015 alle 17:57, Trevor Daniels > ha scritto: >> I've not heard anything from Federico or Josiah for over a week, so >> I've no idea what state Allura at Savannah is in. I sugges

Re: Allura API

ssues/4584 > > returns the JSON representation of ticket 4584. Export provides the JSON representation of the entire DB. I use that to change the original author from *anonymous to GoogleImporter before re-importing, so the whole world doesn't have write access. Trevor _

Re: Allura API

't demonstrate > much. > > http://philholmes.net/lilypond/allura/ Promising start, Phil! Shows you've mastered the authentication and API documentation. No mean feat. I think you've found status:Started && _patch:review, rather than just sta

Re: New bug tracker?

g tracker at Savannah, and this is being set up at present. In the meantime we have an interim bug tracker for use by developers only, so we can keep track of changes. I'd rather not direct users to this temporary arrangement to avoid confusion

Re: Allura at SF is ready

James Lowe wrote Monday, August 31, 2015 9:29 AM > @Trevor > > Assuming that you eventually start the migration, I assume you'll tell > the group and we'd best hold off updating SF until it is completed (so > that we don't interfere with the migration)? Yes, that

Learning about Allura

rce code should be either indented by four spaces or a tab. Alternatively, insert a line containing 4 (or more) tildes before and after the Lily code. As an example, see https://sourceforge.net/p/testlilyissues/issues/4581/ before Simon works out

Bug Squad invited to join Allura

27;ve chosen so I can add you as a developer. If you are spam-averse I suggest you use a disposable email address so you can make a clean break after we move to Savannah. The intention is to migrate the data from SF (not GC) to Savannah, so any work you do now will be preserv

Re: lilypond.org - file storage

am, I prefer not to delete history if it can be avoided, although it is clearly more important to make sure we can continue running smoothly. What you suggest sounds very sensible. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://li

Re: Allura at SF is ready

on line soon. Are you willing to update the DB with pushes when they occur for a few days? Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [testlilyissues:issues] #4579 NR Changing Defaults: Explain sticky contexts accurately

why I asked Simon to add his first, as he'd already bagged the next four serial numbers. Ah well - just shows we'd better start using the new Allura DB properly ASAP so there is just one authoratative source. We'll have to ignore Simon'

Re: Allura at SF is ready

hich is inappropriate (and incorrect). I've defined " " as the default for this field; should be OK for new issues now. That also reminded me to define defaults for other fields too. > Otherwise it seems simple enough. Thanks! Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: lilypond.org - file storage

lease now, IMO. That should free up enough space for the moment. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allura at SF is ready

David Kastrup wrote Saturday, August 29, 2015 11:12 AM > "Trevor Daniels" writes: > >> David Kastrup wrote Saturday, August 29, 2015 10:34 AM >> >>> Sounds more like a job for a script. >> >> It would be tricky. The script would need to f

Re: Allura at SF is ready

David Kastrup wrote Saturday, August 29, 2015 10:34 AM > "Trevor Daniels" writes: > >> What doesn't work is a link to a specific comment. They take you >> back to the start of the issue, not the comment. But as the old >> comments are all linear i

Re: Allura at SF is ready

Pál, you wrote Saturday, August 29, 2015 8:21 AM > > 2015-08-28 21:32 GMT+02:00 Trevor Daniels : >> >> There is a link field available in every comment to cut and >> paste in order to refer to it from elsewhere, including other >> issues, when threading doesn't

Re: Allura at SF is ready

e not needed so often. There is a link field available in every comment to cut and paste in order to refer to it from elsewhere, including other issues, when threading doesn't meet the need. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Allura at SF is ready

the Patchy and push details up to date. You may even be able to use it to help with the countdown this weekend. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: New issue submission process?

whether to ask all developers to use the SF implementation. Maintaining it by proxy cannot go on for long. > Does anyone besides myself need some explanation / explication? I've sent a few mails to the dev list. Apologies for not copying the bug list. Trevor ___

Re: Moving the Issues DB to Allura

; Now I'm greeted with ads as I go to the project page. SF is hardly more commercial than Google anyway, although the ads are a nuisance, granted. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Moving the Issues DB to Allura

David Kastrup wrote Tuesday, August 25, 2015 4:04 PM > "Trevor Daniels" writes: > >> I'll use one of the existing testing projects. The display name is >> readily editable anyway to something like "LilyIssues", although not >> the url.

Re: Moving the Issues DB to Allura

David, you wrote Tuesday, August 25, 2015 2:57 PM > > "Trevor Daniels" writes: > >> I'll create a new project - LilyPond - at SourceForge and begin the >> migration for real later today. If Allura at Savannah becomes >> available within the next few

Moving the Issues DB to Allura

re so registered already). I'll create a new project - LilyPond - at SourceForge and begin the migration for real later today. If Allura at Savannah becomes available within the next few days it should be easy to transfer. Trevor ___ lilypond-devel ma

Re: PATCHES: Countdown for August 26th 2015 - IMPORTANT UPDATE TO PATCHREVIEW PROCESS - PLEASE READ

re-import, which will take another c. 35 hours. To do this, I'll use the VM at Savannah if it is ready; otherwise I'll use the system at SF. So the earliest date at which we can hope to move all issue activity to Allura is next week-end, 29/30 Aug. If

Re: Migrating the Issues DB from Google Code to Savannah

r than recording the resulting pushes. I'll start the final import of the DB to SF on Wed 26 Aug 2015. It may take some days to succeed, depending on load, so we should assume we have no tracker available for the whole of w/b 24 Aug 2015. Until it works everyone will have to either stop

Re: Migrating the Issues DB from Google Code to Savannah

David Kastrup wrote Thursday, August 20, 2015 10:37 AM Subject: Re: Migrating the Issues DB from Google Code to Savannah > "Trevor Daniels" writes: > >> I suggest doing the final countdown, and then stop updating the issues >> DB other than recording the resul

Re: Let \addlyrics accept an optional context mod (issue 255610043 by...@gnu.org)

ld be expanded to include the table you mention. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [Lilypond-auto] Issue 4536 in lilypond: Doc: Usage - tidy up ofexternal.itely file

x27;patch. Hi James Could you please add a link to the Rietveld patch. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Migrating the Issues DB from Google Code to Savannah

at Savannah as soon as possible. So where do we stand in installing Allura on the VM and in redeveloping our scripts to work with Allura? Are Federico and Carl respectively still working on these aspects? Trevor ___ lilypond-devel mailing list lilypond

Re: Issue 4495 Remove unnecessary #{ .. #} constructs (issue 253310043 by tdanielsmu...@googlemail.com)

d...@gnu.org wrote Saturday, July 18, 2015 11:02 PM > One thing that you have to be aware of is that > #{ \music #} > is not equivalent to music but rather to > (ly:music-deep-copy music (*location*)) > since it creates a copy of the music and puts the point-and-click > information to the call o

Re: Implement partial function calls. (issue 249670043 by d...@gnu.org)

Werner LEMBERG wrote Saturday, July 11, 2015 7:36 PM >> And \{ ... \} seem nice to leave open for used-defined >> articulations. > > I favour \etc also. Me too. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org htt

Re: [gnu-advisory] Request for a VM hosting Allura bugtracker forGNU LilyPond

Not trivial when this is a server open to the world, and needing to be properly secured. Perhaps we should clarify this first, unless someone already knows the answers. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [gnu-advisory] Request for a VM hosting Allura bugtracker forGNU LilyPond

have met the nuisance of having to import, export and re-import the DB just to change the author from *anonymous to googleimporter. A process that seems to fail much more often than it succeeds. That would be an easy fix to apply if we had compile ability. Trevor

Re: [gnu-advisory] Request for a VM hosting Allura bugtracker forGNU LilyPond

alf a Gb is not much these days. No idea about memory requirements. Maybe Federico could help, as I believe he has installed Allura. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Request for a VM hosting Allura bugtracker for GNU LilyPond

Werner, you wrote Sunday, June 14, 2015 10:11 AM > > Dear Advisory Committee, > [snip] > We now ask you to provide us a VM so that we can install (and > maintain) Allura by ourselves, not being a burden to the Savannah > people. Thanks! Cros

Re: What's up with input/regression/page-spacing.ly ?

e096ee0e8bcc1af1 I suspect some of the others are the result of Joe re-writing the page-spacing algorithms without changing the regression test. That was in 2009. And I think other changes to these properties have been made over the years. Trevor _

Re: lilypond hosting future

a lead in requesting a VM via gnu-advis...@gnu.org? Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: git-cl upload has stopped working (so has patchy)

Trevor Daniels wrote Tuesday, June 02, 2015 3:03 PM > Trevor Daniels wrote Tuesday, June 02, 2015 10:39 AM >> >> Trevor Daniels wrote Tuesday, June 02, 2015 8:51 AM >> >>> Werner LEMBERG wrote Tuesday, June 02, 2015 4:30 AM >>> >>>> Thanks

Re: git-cl upload has stopped working (so has patchy)

Trevor Daniels wrote Tuesday, June 02, 2015 10:39 AM > > Trevor Daniels wrote Tuesday, June 02, 2015 8:51 AM > >> Werner LEMBERG wrote Tuesday, June 02, 2015 4:30 AM >> >>> Thanks for your efforts! But what about images? Just for testing, I >>> open

Re: git-cl upload has stopped working (so has patchy)

Trevor Daniels wrote Tuesday, June 02, 2015 8:51 AM > Werner LEMBERG wrote Tuesday, June 02, 2015 4:30 AM > >> Thanks for your efforts! But what about images? Just for testing, I >> opened issue 4266 in both googlecode and SF. >> >> https://code.google.com/p/

Re: git-cl upload has stopped working (so has patchy)

horised change. As Phil said, not a show-stopper, but clearly undesirable. I'll investigate. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: git-cl upload has stopped working (so has patchy)

Trevor Daniels wrote May 28, 2015 6:18 PM > >> On 27/05/15 21:17, David Kastrup wrote: >> >>> Asked Han-Wen. What's going on is that password authentication is no >>> more with Google. >>> >>> http://googledevelopers.blogspot.ch/2015/02

Re: git-cl upload has stopped working (so has patchy)

This sounds like a sensible approach. >> >> Given the reports that SourceForge distributes Adware (and there >> even have been virus-ridden versions of it) on its Windows >> installers, I'm somewhat wary here. [...] >

Re: git-cl upload has stopped working (so has patchy)

aybe not too difficult, but I've not tried it. Fortunately Allura does all this automatically, although it does take 36 hours, probably due to a activity-limiting control. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: git-cl upload has stopped working (so has patchy)

sting offering downloads from SF. It may be strange to use their project facilities without offering downloads, but I suspect lots of projects there are in development prior to achieving (and probably many are unlikely ever to achieve) a download-capable state. It doesn&

Re: git-cl upload has stopped working (so has patchy)

Federico Bruni wrote Sunday, May 31, 2015 8:14 AM > Il giorno sab 30 mag 2015 alle 20:57, David Kastrup ha > scritto: >> "Trevor Daniels" writes: >> >>> David Kastrup wrote Saturday, May 30, 2015 2:53 PM >>> >>>> At any rate, I ca

Re: [PATCH 1/5] Remove parser/location global variable setup

pect anyway. It will be appreciated in the same way that good health is appreciated after recovering from an illness. Thanks for doing this, David. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: git-cl upload has stopped working (so has patchy)

James Lowe wrote Friday, May 29, 2015 8:08 AM > On 28/05/15 18:18, Trevor Daniels wrote: > >> Given this problem I thought it prudent to see if I could still import the >> Issues DB from GoogleCode to Allura in SourceForge. I started the import at >> 12 noon to

Re: git-cl upload has stopped working (so has patchy)

David Kastrup wrote Saturday, May 30, 2015 2:53 PM > "Trevor Daniels" writes: > >> OK, I'll wait for someone to make these enquiries. The last time I >> interacted with people at Savannah they lost interest as soon as there >> was no response to their re

Re: git-cl upload has stopped working (so has patchy)

David Kastrup wrote Saturday, May 30, 2015 11:13 AM > "Trevor Daniels" writes: > >> Trevor Daniels wrote Thursday, May 28, 2015 6:18 PM >>> >>> James Lowe wrote Thursday, May 28, 2015 7:04 AM >>>> >>>> On 27/05/15 21:17, David

Re: git-cl upload has stopped working (so has patchy)

Trevor Daniels wrote Thursday, May 28, 2015 6:18 PM > > James Lowe wrote Thursday, May 28, 2015 7:04 AM >> >> On 27/05/15 21:17, David Kastrup wrote: >> >>> So now git-cl -n works again. But git cl does not just need to >>> communicate with Rietvel

Re: git-cl upload has stopped working (so has patchy)

sw=1 > > That explains why test-patchy (and probably accept/reject-patchy) don't > work either. Given this problem I thought it prudent to see if I could still import the Issues DB from GoogleCode to Allura in SourceForge. I started the import at 12 noon today (28 May) and after a disconcertingly long pause before anything happened it now seems to be proceeding normally. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Assessment of Allura at SourceForge

see. So it looks like this is not caused by congestion but is just how long it takes to built the Issues DB. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Assessment of Allura at SourceForge

Hi Dan I set the permissions for Developers (you're one) to permit editing comments. Maybe only Admins should have this privilege? Easy to change, but I'll leave it as it is for now. Trevor - Original Message - From: "Dan Eble" To: "Trevor Daniels"

Re: Assessment of Allura at SourceForge

0 mins or so. It's the import that takes an age, typically 36 hours once it starts. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Assessment of Allura at SourceForge

he same search could be (in github for example): > is:open is:issue label:Documentation partcombine > > No capital letters, no parentheses, no redundant stuff. That looks worth trying, so I did: Error running search query: [Reason: undefined fi

Re: Assessment of Allura at SourceForge

Trevor Daniels wrote Sunday, May 17, 2015 9:33 AM Subject: Assessment of Allura at SourceForge > Hi > > I've now completed my assessment of Allura at SourceForge against the list of > requirements supplied by Phil. > > There are some differences from GoogleCode, but the

Re: Add French-specific note names (issue 239930043 byv.villen...@gmail.com)

er in the required font, and cut and paste it. Here it is: ñ The only characters under Alt Gr are acute accent vowels: áéíóú. No idea what code is generated. Pretty sure it isn't unicode. You can see why we seem to be lazy ;) Trevor ___ lilypo

Assessment of Allura at SourceForge

ference. (See 15) > 17. Email updates to (preferably) lilypond-a...@gnu.org Available as standard. > 18. Allow users to watch an issue and be informed of updates by email Any user who comments or votes on an issue is automatically informed of further changes to that issue. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Google Code shutting down

27;m not familiar with Savane so I can't make a detailed comparison, but I believe it does not support images and does not have a GoogleCode importer. Does it also not have an API? Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org ht

Re: Google Code shutting down

Trevor Daniels wrote Saturday, May 16, 2015 10:44 AM > > I've pretty well completed my assessment of Allura at SourceForge, and find > the facilities available pretty well match our needs, in fact they are > surprisingly similar to those at GoogleCode. There are some differ

Re: Google Code shutting down

Trevor Daniels wrote Saturday, May 16, 2015 12:27 PM > > David Kastrup wrote Saturday, May 16, 2015 11:11 AM > >>> Trevor Daniels wrote Tuesday, May 12, 2015 9:15 PM >>> >>>> I'm sure we'll find some undesirable features of Allura when we get

Re: Google Code shutting down

David Kastrup wrote Saturday, May 16, 2015 11:11 AM >> Trevor Daniels wrote Tuesday, May 12, 2015 9:15 PM >> >>> I'm sure we'll find some undesirable features of Allura when we get >> down to the details, but that's what the next few weeks will te

Re: Google Code shutting down

Phil Holmes wrote Saturday, May 16, 2015 11:17 AM > >> Trevor Daniels wrote Tuesday, May 12, 2015 9:15 PM >> >>> I'm sure we'll find some undesirable features of Allura when we get down >>> to the details, but that's what the next few weeks w

Re: Google Code shutting down

Trevor Daniels wrote Tuesday, May 12, 2015 9:15 PM > I'm sure we'll find some undesirable features of Allura when we get down to > the details, but that's what the next few weeks will tell us. I've pretty well completed my assessment of Allura at SourceForge, and find

Re: Compile LilyPond for NaCl

Does any of the work done at https://code.google.com/p/naclports/wiki/PortList mean anything for LilyPond? On Wed, May 13, 2015 at 2:52 PM Carl Sorensen wrote: > > > On 5/13/15 12:01 PM, "Simon Albrecht" wrote: > > >Am 13.05.2015 um 18:50 schrieb Carl Sorensen: >

Compile LilyPond for NaCl

Could any useful part of LilyPond be compiled for NaCl ? Is that at all within the realm of possibility? ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.or

Compile LilyPond for NaCl

Could any useful part of LilyPond be compiled for NaCl ? Is that at all within the realm of possibility? ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.or

Re: Google Code shutting down

James wrote Tuesday, May 12, 2015 1:46 PM > >> Trevor > Do we even need a new git-cl? > > I am no expert but wasn't that designed to get around the fact that we > had to upload to two different places (one place for actual review and > one for a note on the track

Re: Google Code shutting down

Carl, you wrote Tuesday, May 12, 2015 8:45 PM > On 5/11/15 11:06 AM, "Trevor Daniels" wrote: >>The second, with 4369 issues, is >>https://sourceforge.net/p/testlily/issues/ I've not done anything to >>tailor this to our needs yet. I intend to do that over t

Re: Google Code shutting down

Carl Sorensen wrote Tuesday, May 12, 2015 8:32 PM >>On 11/05/15 23:04, Trevor Daniels wrote: >>> Phil Holmes wrote Monday, May 11, 2015 6:21 PM >>> >>>> Have you investigated the API for patch and git-cl? >>> I've quickly looked at Allura's

Re: Google Code shutting down

#x27;s API. It seems to contain all the features we would need. I've also looked at git-cl, but unpicking that is someway outside my comfort zone. It's built around code obtained from Google. I don't plan to work on git-cl's conversion, so we need some other volunteer to do

Re: Google Code shutting down

Phil Holmes wrote Monday, May 11, 2015 4:37 PM > > Trevor Daniels wrote Wednesday, May 06, 2015 10:05 PM >> >> As to the match of Allura to our needs, AFAICS it can provide everything >> in Phil's requirements list except for the automatic handling of blocked >&

Re: Google Code shutting down

Trevor Daniels wrote Wednesday, May 06, 2015 10:05 PM > I'm just importing the issue DB at the moment. I've now tried twice to import our Issue DB from GoogleCode to Allura at SourceForge. As previously reported the first attempt failed after 1112 issues. The second attempt als

Re: Google Code shutting down

a few days. I'm just importing the issue DB at the moment. Trevor ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Combining \layout variables

David, you wrote Tuesday, May 05, 2015 8:00 PM > "Trevor Daniels" writes: > >> David, you wrote Tuesday, May 05, 2015 7:14 PM >> >> >>> "Trevor Daniels" writes: >>> >>>> David Kastrup wrote Tuesday, May 05, 2015 5:44

Re: Combining \layout variables

David, you wrote Tuesday, May 05, 2015 7:14 PM > "Trevor Daniels" writes: > >> David Kastrup wrote Tuesday, May 05, 2015 5:44 PM >>> >> >>> "Trevor Daniels" writes: >>> >>>> The answer to both these questions is

Re: Combining \layout variables

David Kastrup wrote Tuesday, May 05, 2015 5:44 PM > > "Trevor Daniels" writes: > >> The answer to both these questions is that the satb.ly template >> comes after the user's code in the input file. So the overriding >> operates the wrong way round. &g

Re: Combining \layout variables

't that work in your use scenario? > > What is wrong with setting a layout definition in the satb.ly template > that then gets amended by the user? > The answer to both these questions is that the satb.ly template comes after the user's code in the input file. So the ov

Re: Lilypond Issue handling system draft requirements

ent might be better written as: 14. Allow export of the issue database as a zipped JSON file containing all the index variables and discussion text, together with a means of accessing all attachments so these may be re-associated correctly with the relevant t

Re: Combining \layout variables

David, you wrote Tuesday, May 05, 2015 3:57 PM > "Trevor Daniels" writes: > >> Multiple layout blocks can be combined in sensible ways, with later >> definitions taking precedence over earlier ones on an item by item >> basis, but the same is not true

Combining \layout variables

What I would like to do is to combine two layout blocks contained in variables in the same way as layout blocks at top level are combined, item by item, but it seems this is not possible, at least I haven't been able to achieve it. Is this indeed not possible? T

Re: Google Code shutting down

Carl Sorensen wrote Monday, May 04, 2015 11:44 PM > On 5/4/15 3:44 PM, "Trevor Daniels" wrote: >> >>Trevor Daniels wrote Monday, May 04, 2015 10:01 PM >> >>> OK, I've created a project on SourceForge and started >>> downloading the i

<    1   2   3   4   5   6   7   8   9   10   >