Re: Rebasing core-updates-next branch

[Ricardo Wurmus]

Ludovic Courtès <address@hidden> writes:

> Hi!
>
> Manolis Ragkousis <address@hidden> skribis:
>
>> Core-updates-next has not been updated for some time so I think it's
>> time to do that.  I was planning to rebase core-updates-next on
>> core-updates and create a new core-updates-next.
>>
>> There is a problem though. Rebasing changes the pgp signature of the
>> commit. The affected commits are the ones below.
>>
>> a08539d gnu: guile: Use "site-ccache" for the compiled search path.
>> 14af4d1 build: Correctly determine the system type for GNU/Hurd systems.
>> 5b32f07 gnu: wrap-python3: Create more symlinks.
>> 788eb97 gnu: sqlite: Update to 3.13.0.
>> bd46fdc utils: Fix 'modify-phases' docstring.
>> d35bc36 gnu: curl: Update to 7.49.1.
>> 98e8dc6 packages: Use '--no-backup-if-mismatch' for patching.
>>
>> I have cc'ed the authors of those commits.  If you are okay with it, I
>> will sign those commits with my key and push the new core-udpates-next.
>
> Fine with me!
>
> Ricardo Wurmus <address@hidden> skribis:
>
>> Do we need to rebase?  Is a merge not possible?
>
> I like to avoid unnecessary merge commits, but I could go either way in
> this case.  I guess you’d prefer merging?

Either way is fine by me (and my commits are not affected here).  I just
think that it’s a bit unfortunate to throw away signatures.

~~ Ricardo