Thank you, Urs and Simon. I have begun taking a look at the git process, and
will continue to dive into those posts. Very exciting, regardless!
~Conor
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Git-Lilypond-workflow-tp171764p171989.html
Sent from the User mailing
n sure whether you'd need Git at all that's definitely
> nothing for you yet.
>
> As to your final question: The purpose of using Git is keeping track of
> changes. And that makes the difference. I always say: making the move to
> use version control for authoring documents
authoring documents (scores and text) is like
learning to read or learning to walk.
Best
Urs
~Conor Cook
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Git-Lilypond-workflow-tp171764p171935.html
Sent from the User mailing list archive at Nabble.com.
orical posts on lilypondblog.org on
this topic (search for version control), which should summarise the
reasons quite well.
Yours, Simon
~Conor Cook
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Git-Lilypond-workflow-tp171764p171935.html
Sent from the User mailing list archiv
with a symbolic link to
access the files I need on both computers (with the hard file on my laptop,
which stays at home).
Basically, what is the purpose of using Git other than keeping track of
changes?
~Conor Cook
--
View this message in context:
http://lilypond.1069038.n5.nabble.com/Git-Li
I use Git and Lilypond. I know Git quite well, but haven't been using
Lilypond much lately. I can see from this thread that I'm not using the
two together efficiently, so I'll describe what I should be doing.
1) Keep a "tools" repository with the include files I depend on, and
really should
I use one repository, a number of shared directories, and then one
subdirectory for each project.
I create a branch off of my master branch whenever I start a project (and
often a number of branches off of that for experiments) and make a lot of
commits, then I rebase and squash all the commits i
Thanks for the advice everyone. I appreciate your experience.
Craig
On Fri Feb 13 2015 at 8:24:28 AM H. S. Teoh wrote:
> On Thu, Feb 12, 2015 at 02:07:36PM -0800, Tim Walters wrote:
> [...]
> > Different strokes, I guess!
>
> Indeed. :-)
>
>
> > On 2/12/15 1:44 PM, H. S. Teoh wrote:
> > >It's
On Thu, Feb 12, 2015 at 02:07:36PM -0800, Tim Walters wrote:
[...]
> Different strokes, I guess!
Indeed. :-)
> On 2/12/15 1:44 PM, H. S. Teoh wrote:
> >It's not *that* much easier than `mkdir new_composition; cd
> >new_composition; git init`. :-)
>
> Then you have to push it to the remote serve
Op Thu, 12 Feb 2015 20:33:31 +
Craig Dabelstein schreef:
> Hi list,
>
> Would anyone be able to briefly share with me how they use Git with
> Lilypond; i.e. do you create a separate repository for each
> composition you are working on, do you make a separate branch for
> each part while you
On 2/12/15 1:44 PM, H. S. Teoh wrote:
If it were me, I'd use a dedicated repository for the common stuff, put
it in a specific location, and just point the scripts in each
composition's directory at it.
All well and good until you want to branch it with a composition, set up
a new machine, etc
On Thu, Feb 12, 2015 at 01:29:55PM -0800, Tim Walters wrote:
> My approach is almost the opposite. I have everything in one
> repository, with each composition in its own folder, because:
>
> --I have files that are common to all compositions. Having separate
> copies of these all over the place i
My approach is almost the opposite. I have everything in one repository,
with each composition in its own folder, because:
--I have files that are common to all compositions. Having separate
copies of these all over the place is exactly what I don't want. If I
change, for example, the script t
Hi Craig,
I have a quite primitive git workflow:
Two repos:
1. openlilylib snippets (with some private branches)
2. scores (containing all my scores in different subfolders)
In (1) I have some branches for each additional feature, to stay in sync with
the upstream repository
In (2) I just commit
Hi,
I'm a software engineer by trade and have been using git for software
development for quite some time.
Let me first start saying that there are *many* different possible
workflows, and each user needs to come up with their own workflow that
they're comfortable with.
With respect to branching
On Thu, Feb 12, 2015 at 08:33:31PM +, Craig Dabelstein wrote:
> Hi list,
>
> Would anyone be able to briefly share with me how they use Git with
> Lilypond; i.e. do you create a separate repository for each
> composition you are working on, do you make a separate branch for each
> part while y
Hi list,
Would anyone be able to briefly share with me how they use Git with
Lilypond; i.e. do you create a separate repository for each composition you
are working on, do you make a separate branch for each part while you are
working on it and then merge when it is finished, if you sell your musi
17 matches
Mail list logo
