Wols Lists writes:
> On 07/06/18 23:36, David Kastrup wrote:
>> Thomas Morley writes:
>>
>>> One additional question: If I want to add something to the then
>>> updated branch, would
>>> $ git push origin HEAD:dev/guile-v2-work
>>> work or would I need to follow the route you described above?
>
2018-06-08 0:40 GMT+02:00 Thomas Morley :
> 2018-06-08 0:36 GMT+02:00 David Kastrup :
>> Thomas Morley writes:
>>
>>> One additional question: If I want to add something to the then
>>> updated branch, would
>>> $ git push origin HEAD:dev/guile-v2-work
>>> work or would I need to follow the route
On 07/06/18 23:36, David Kastrup wrote:
> Thomas Morley writes:
>
>> One additional question: If I want to add something to the then
>> updated branch, would
>> $ git push origin HEAD:dev/guile-v2-work
>> work or would I need to follow the route you described above?
>
> As long as you don't reba
"James Lowe" writes:
> Hello,
>
> On Fri, 8 Jun 2018 00:40:46 +0200, Thomas Morley
> wrote:
>
>> 2018-06-08 0:36 GMT+02:00 David Kastrup :
>> > Thomas Morley writes:
>> >
>> >> One additional question: If I want to add something to the then
>> >> updated branch, would
>> >> $ git push origin H
Hello,
On Fri, 8 Jun 2018 00:40:46 +0200, Thomas Morley
wrote:
> 2018-06-08 0:36 GMT+02:00 David Kastrup :
> > Thomas Morley writes:
> >
> >> One additional question: If I want to add something to the then
> >> updated branch, would
> >> $ git push origin HEAD:dev/guile-v2-work
> >> work or wo
2018-06-08 0:36 GMT+02:00 David Kastrup :
> Thomas Morley writes:
>
>> One additional question: If I want to add something to the then
>> updated branch, would
>> $ git push origin HEAD:dev/guile-v2-work
>> work or would I need to follow the route you described above?
>
> As long as you don't reba
Thomas Morley writes:
> One additional question: If I want to add something to the then
> updated branch, would
> $ git push origin HEAD:dev/guile-v2-work
> work or would I need to follow the route you described above?
As long as you don't rebase, your followup work is a descendant of the
previo
2018-06-07 23:48 GMT+02:00 David Kastrup :
> Thomas Morley writes:
> If you are really sure that your branch's commits are fine,
Well, I'm not sure my additional patches are the best possible ones,
rather I'm sure they are not.
Though, this _is_ an experimental branch to check for and experiment
Thomas Morley writes:
> (3) updating it
>
> $ git rebase master
> [skipping output, resolving merge-conflicts, applying additional patches]
>
>
> (4) attempt to push in order to make the updates public
>
> $ git push origin HEAD:dev/guile-v2-work
> To ssh://thomasmor...@git.sv.gnu.org/srv/git/lil
Hi,
as said here
http://lilypond.1069038.n5.nabble.com/lilypond-not-working-when-compiled-against-guile-2-2-tt213540.html#a213599
I tried to update the branch dev/guile-v2-work, but failed so far.
I did:
(1) the branch:
$ git branch -a
=>
[ skipping lots of branches ]
remotes/origin/dev/guile
10 matches
Mail list logo