This is my first post to the discussion list and it is more of a
question about the clarity of a scanned source I am working on.
Please let me know if these questions are not appropriate to the
mailing list.
I am working from Boije 4, D. Aguado's Op4 Six Petites
My last push did the same thing --- merged my push into my most recent pull
request. I'm familiar enough with git but need to figure out how to control
the github behavior.
-glen
On Sun, Dec 9, 2012 at 12:49 PM, Chris Sawer ch...@mutopiaproject.orgwrote:
On 04/12/12 08:07, Federico Bruni
Ah, thanks for the hint, Felix. if you have a pull request from your fork's
master any subsequent commit before that pull request is handled is
considered part of that pull request. I was creating branches on my local
repository, then merging them locally. I need to adjust my workflow.
On Sun,
Very cool, David.
Felix, I knew you'd want something like this made out of that:
Simple python wrapper for this scheme code https://gist.github.com/4480245
On Mon, Jan 7, 2013 at 7:59 AM, David Kastrup d...@gnu.org wrote:
Felix Janda felix.ja...@posteo.de
writes:
Hi,
just some
On Thu, Jan 9, 2014 at 11:11 PM, Glen Larsen glenl@gmail.com wrote:
I have started an update project in the Mutopia GIT repository and this is
a request for assistance. There are 15 files in the archive that are
written for LilyPond versions less than 2.0 and I have entered each one of
them
Valentin,
Thanks for this. It is always interesting to see how others get along with
this task.
On Mon, Jan 20, 2014 at 1:36 AM, Valentin Villenave
valen...@villenave.netwrote:
[ snip ]
- Similarly, one has to remind that basic markups were used for
practically everything, so you might want
It has been a little over 2 weeks since this task was started and I am
happy to say that 14 of the 15 tasks have pull requests submitted. A big
Thank You! to the volunteers who helped get Mutopia clear of LilyPond 1.x:
Karsten Richter
Valentin Villenave
Javier Ruiz-Alma
Francisco Vila
Federico
) Action 2.18 update pull requests I intend to
have these finished by the end of February. Sorry that it means waiting a
bit longer for the 2.18 updates but once the updating is more automated I
should be able to process them more quickly in the future. Regards, Chris
On 25/01/14 17:26, Glen Larsen
to accept the challenge and engage users on mutopia-discuss
if you get stuck.
-glen
On Tue, Feb 18, 2014 at 3:07 AM, Philip Rhoades p...@pricom.com.au wrote:
Glen,
On 2014-02-18 18:16, Glen Larsen wrote:
I have begun another set of updates --- 15 files --- for the Mutopia
Project
converted from 2.0 to 2.14!
Thanks,
-glen
On Mon, Feb 17, 2014 at 11:16 PM, Glen Larsen glenl@gmail.com wrote:
I have begun another set of updates --- 15 files --- for the Mutopia
Project and volunteers are welcome. When complete, we will have cleared the
archive of all pieces built
It was interesting to review how differently Bach's French
Suiteshttp://www.mutopiaproject.org/cgibin/make-table.cgi?collection=bachfrpreview=1and
English
Suiteshttp://www.mutopiaproject.org/cgibin/make-table.cgi?collection=bachengpreview=1are
presented in Mutopia collections. The French Suites
I have enjoyed these update projects and plan more of them in the future.
Right now I am absorbed in a transcription of Chopin's Nocturne, op 9, no 3
and I hope to get that done before moving house in about a month.
When all that dust clears I hope to get another update chunk started.
Until
In Mutopia there is typically no real need to merge other updates into a
development branch because [1] it doesn't have dependencies to other parts
of the Mutopia archive and [2] changes to a single piece within the archive
are done by a single individual.
I would prefer a minimal number of
On Wed, May 14, 2014 at 8:17 AM, Knute Snortum ksnor...@gmail.com wrote:
In
https://github.com/chrissawer/The-Mutopia-Project/wiki/Setting-up-for-Contributions-via-GITHUB
Under Synchronize with your local repository,
Couldn't
$ git fetch upstream$ git merge upstream/master
be
Of course this will work --- master is a branch like any other branch and
you could specify master in your pull request. It is not recommended
practice because:
- You now have to wait until that pull request is processed to submit
other work
- If you now create a branch that change is
On Wed, May 14, 2014 at 11:23 AM, Knute Snortum ksnor...@gmail.com wrote:
Thanks Felix, I'll try that.
If I can close a pull request, I don't see how to on GitHub. I may just
be missing it, though. If anyone knows how to do it, please tell me.
Closing is a product of merging the pull
This is a request for volunteers to participate in another series of
updates for the Mutopia Project archive. The 27 pieces in this set are all
built with LilyPond version 2.1.*.
Each target piece is entered as a GITHUB issue. This GITHUB milestone
tracker
At this time there are only 5 pieces available for assignment in the phase
3 update task. It has been 2 days since the task was announced and the team
has generated 14 pull requests.
At the completion of this task the Mutopia Project archive will have no
pieces built with LilyPond older than
Ah, so right. My apologies for not doing deeper research. I'll take a more
complete look later today.
On Thu, Dec 4, 2014 at 3:12 AM, Federico Bruni f...@inventati.org wrote:
Il giorno gio 4 dic 2014 alle 8:00, Glen Larsen glenl@gmail.com ha
scritto:
These instructions are modifying
Taking a look at the title page on google books I would say that the source
field in the header should read:
source = Price Reynolds, 41, Berners Street W, London
This, along with the publication date, provide a clear statement of what
you used as a base for this transcription.
You may want
I'm starting a new set of transcriptions, Aguado's Op. 3, and since this is
only 8 small pieces, is there a preference for the work to be presented as
one document of the entire opus, or 8 individual documents? (I prefer
single pieces since I rarely print an entire opus at home.)
Also, I am
2.10 454
2.11 308
2.12 186
2.13 27
2.14 75
2.16 314
2.17 1
2.18 209
2.19 59
Lots of work to do to get to the 2.8 area but nothing like the 2.10 - 2.12
hurdle.
On Thu, Aug 27, 2015 at 10:20 PM, David Kastrup d...@gnu.org wrote:
Glen Larsen
22 matches
Mail list logo
