lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: LilyPond GSoC logistics


From: Urs Liska
Subject: Re: LilyPond GSoC logistics
Date: Thu, 21 May 2020 19:43:28 +0200
User-agent: K-9 Mail for Android


Am 21. Mai 2020 19:21:27 MESZ schrieb Owen Lamb <address@hidden>:
>>
>> To preserve your code within LilyPond it probably makes sense if you
>put
>> your code into a private (but public) branch of the upstream lilypond
>> repository (i.e., not a gitlab clone of it), for example
>> 'dev/lamb/GSoC-2020'.
>>
>
>I'm a bit confused here, so let me just make sure I understand what
>you're
>saying
>
>I'll be making a new branch titled "dev/lamb/GSoC-2020" in the GitLab
>repository, based off the current master. It will be "private" in the
>sense
>that it's my personal workspace (hence the "lamb" namespace), but it
>will
>be "public" in the sense that it will be visible to the public. It will
>not
>be merely "a gitlab clone" of the master branch, since it is a new
>branch
>entirely. Did I interpret that correctly?

Yes, that should be how it is.

I think the message should read "not a fork". A fork is a personal copy that 
you need when you don't have push access to a repository.

A "clone" in Git-speak is the local copy you are actually working in. Of course 
you will have such a clone. 

HTH 
Urs


>
>I'm pretty new to git, so please excuse my lack of expertise!

-- 
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]