lilypond-devel
[Top][All Lists]
Advanced

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

Re: GUB with local git-repo?


From: Phil Holmes
Subject: Re: GUB with local git-repo?
Date: Sat, 8 Jun 2019 12:10:07 +0100

----- Original Message ----- From: "Thomas Morley" <address@hidden>
To: "David Kastrup" <address@hidden>
Cc: "Phil Holmes" <address@hidden>; "lilypond-devel" <address@hidden>
Sent: Saturday, June 08, 2019 7:30 AM
Subject: Re: GUB with local git-repo?


Phil, David,

thanks for the hints

Am Fr., 7. Juni 2019 um 13:40 Uhr schrieb David Kastrup <address@hidden>:

Thomas Morley <address@hidden> writes:

> Hi Phil,
>
> let's see, if I understand correctly:
>
> For a public branch, I'd checkout a local branch, say: dev/issue4943
> Then make it public with
>   git push origin dev/issue4943
> Further changes added to this branch with
>   git push dev/issue4943 HEAD:staging

What?  No, just continue with

    git push origin dev/issue4943

> Invoking GUB with
>   make LILYPOND_BRANCH=dev/issue4943 lilypond
>
> Though, I don't know how to delete said branch from the official repo,
> after all work is done.

git push origin :dev/issue4943

Basically, push an empty ref.

Seems a bit strange that one can only work through the official
repository.

Here I don't understand what you mean, could you explain more detailed?

I think David is suggesting it's strange that GUB can only use the Savannah repo, not any git repo of your choice. TBH I'm not sure whether it's a configuration item or hard wired into the GUB code. For me, an even bigger problem is that GUB only does partial builds from master, not a branch of choise.

Can't you just clone a repository for which "origin" is
your local repository rather than the official upstream?

Cheers,
 Harm


--
Phil Holmes



reply via email to

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