Re: How to update a remote branch (remotes/origin/dev/guile-v2-work)

[David Kastrup]

"James Lowe" <address@hidden> writes:

> Hello,
>
> On Fri, 8 Jun 2018 00:40:46 +0200, Thomas Morley <address@hidden> wrote:
>
>> 2018-06-08 0:36 GMT+02:00 David Kastrup <address@hidden>:
>> > Thomas Morley <address@hidden> 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
>> > previous work and can be pushed without deletion.
>> >
>> > --
>> > David Kastrup
>> 
>> Ok
>> I'll check for `make doc' tomorrow and, if successful, will push the
>> rebased branch afterwards.
>
> If this works (the 'make doc' that is) should I be starting to 'use'
> Guile 2.whatever to test patches now?

Not generally.  And if doing so for specific cases causes problems,
there seems little point in doing so, at least not before 2.20 is out.

-- 
David Kastrup