Re: Updating gnulib sub-repository (was: Plans for Octave 6.1 release)

[Kai Torben Ohlhus]

On 12/11/19 4:01 AM, Rik wrote:
> On 12/10/2019 10:59 AM, "Markus Mützel" wrote:
>> Am 08. Dezember 2019 um 15:12 Uhr schrieb "Markus Mützel":
>>> Am 07. Dezember 2019 um 21:49 Uhr schrieb "Markus Mützel":
>>>> Am 06. Dezember 2019 um 23:01 Uhr schrieb "Rik":
>>>>> The checklist of instructions is at etc/RELEASE.CHECKLIST and the
>>>>> accompanying bug fix template is at etc/RELEASE.BUG_FIX_LIST. 
>>>>> Traditionally I have placed these as pages on the Octave Wiki at
>>>>> https://wiki.octave.org/Category:Development so that everyone could see 
>>>>> the
>>>>> status, and make changes without requiring excessive permissions.  I have
>>>>> started things off by performing action item #1 : updating gnulib repo.
>>>> That doesn't seem to have worked. There was activity in their git 
>>>> repository during the last 8 months:
>>>> http://git.savannah.gnu.org/gitweb/?p=gnulib.git
>>>>
>>>> I don't know how to import those changes to our hg sub-repo though.
>>> I pushed the following change to the instructions:
>>> http://hg.savannah.gnu.org/hgweb/octave/rev/873ef98668d1
>>>
>>> This worked correctly for me locally. But I haven't actually pushed any 
>>> changes in case this isn't the preferred procedure.
>>>
>>> It might also be possible to get rid of the first lengthy hg convert of the 
>>> complete repository (~1 hour on my hardware). But I'm not familiar with 
>>> git. It would probably work if we could derive the information for the 
>>> splicemap directly from the git repository.
>> The most important step of the procedure is still missing:
>> I don't how to push to the gnulib sub-repo.
>>
>> Markus
> 
> jwe or Mike probably know what the correct procedure is.
> 
> --Rik
> 


Maybe the gnulib hg subrepo can be obsoleted for 6.1, see my changeset
in bug #57044 [1].

Best,
Kai

[1] https://savannah.gnu.org/bugs/index.php?57044#comment10