Yes, I started using Git for the same reason several months ago, and I'm
still thrilled by the implications this has.
It is really perfect to be able to version-control ones sources.
But it's even better for collaborating - working together at the same
files while nearly not having to worry about conflicts.
For the same reason I also started using LaTeX lately - and they form a
very nice trio (LilyPond, LaTeX and Git).
Currently I'm actually only a few commits away from the first _usable_
release of a LaTeX package providing access to LilyPond's notational
elements for use within LaTeX documents ;-)
Re public repositories: Do you know mutopiaproject.org? Is that what you
mean?
Best
Urs
Am 09.11.2012 16:56, schrieb Keehun Nam:
Dear lovely LilyPond community,
I am wondering if there's already a public repository to upload
LilyPond code of full works that are not just useful snippets (which
already exists). If one doesn't already exist, would it be useful for
people if I set one up?
I use Git version control for all my LilyPond files as well as
Dropbox's versioned backups. Does anyone else do the same? This is the
main reason why I use LilyPond--plain text source files compared to
the proprietary formats of Sibelius and Finale. I also use LilyPond to
typeset already-printed scores for extremely clear-er parts and larger
and crisper scores (a lot of it under copyright which wouldn't allow
me to share them). Why do you use LilyPond? Are you all mainly
composers? Music typesetters?
Thank you,
Keehun
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user