From: ludo@gnu.org (Ludovic Courtès)
To: Manolis Ragkousis <manolis837@gmail.com>
Cc: alezost@gmail.com, guix-devel@gnu.org
Subject: Re: Rebasing core-updates-next branch
Date: Tue, 12 Jul 2016 10:56:14 +0200 [thread overview]
Message-ID: <87mvlnkzf5.fsf@gnu.org> (raw)
In-Reply-To: <9cd9387c-589d-5bc2-475b-d12fd6c10ff5@gmail.com> (Manolis Ragkousis's message of "Mon, 11 Jul 2016 16:01:36 +0300")
Hi!
Manolis Ragkousis <manolis837@gmail.com> 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 <rekado@elephly.net> 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?
Thanks,
Ludo’.
next prev parent reply other threads:[~2016-07-12 8:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-11 13:01 Rebasing core-updates-next branch Manolis Ragkousis
2016-07-11 16:02 ` Leo Famulari
2016-07-12 4:45 ` Ben Woodcroft
2016-07-12 6:07 ` Leo Famulari
2016-07-12 6:04 ` Ricardo Wurmus
2016-07-12 7:29 ` Alex Kost
2016-07-12 12:57 ` Manolis Ragkousis
2016-07-12 22:29 ` Leo Famulari
2016-07-12 8:56 ` Ludovic Courtès [this message]
2016-07-12 9:35 ` Ricardo Wurmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mvlnkzf5.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=manolis837@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.