Il giorno mar 13 mag 2014 alle 23:09, Javier Ruiz-Alma
jav...@ruiz-alma.com ha scritto:
Hi Federico,
Glen graciously added instructions on how to setup your github fork,
and basic workflow involved in maintaining existing pieces in Mutopia
using github.
He also a started a document to
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
Frederico, I am confused by what you mean by a merge commit. Since it is
something I should try to avoid, I should understand what it is. Is it
merging a branch into master and committing it?
Glen, I know I'm new to Mutopia. Help me understand why you are using git.
It seems you do not want
Please remove, close, ignore, or whatever you do to get rid of pull
requests for the following:
#382 - promenade 5
#381 - two-jews
#380 - ballet
#379 - Promenade 4
#378 - Bydlo
#377 - Tuileries
#376 - Promenade 3
#375 - Il vecchio castello
#374 - Promenade 2
#373 - Gnomus
#370 - put back nobm
I
I'd like to suggest the following changes to
*The-Mupodia-Project/ftp/MussorgskyM*
1. create a directory called *pictures-at-an-exhibition*
2. Under that, create a directory named *pictures-at-an-exhibition-lys*
3. rename *promenade/promenade.ly http://promenade.ly* to *promenade-1.ly
I brought up the problem here of how to present a set of movements that can
be individually downloaded and yet allow the user to play the suite as a
whole in the correct order. The easiest solution was deemed the best, that
is, rename the movements with numbers as the beginning of their name so
