From: ng0 <ng0@we.make.ritual.n0.is>
To: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: libgcrypt update to 1.7.1
Date: Fri, 17 Jun 2016 18:59:23 +0000 [thread overview]
Message-ID: <20160617185923.GA24906@khazad-dum> (raw)
In-Reply-To: <20160617174302.GA8255@jasmine>
[-- Attachment #1: Type: text/plain, Size: 1120 bytes --]
On 2016-06-17(01:43:02-0400), Leo Famulari wrote:
> On Fri, Jun 17, 2016 at 05:02:44PM +0200, Ludovic Courtès wrote:
> > Efraim Flashner <efraim@flashner.co.il> skribis:
> >
> > > On Thu, Jun 16, 2016 at 11:40:47AM -0400, Leo Famulari wrote:
> > >> On Wed, Jun 15, 2016 at 07:53:28PM +0000, ng0 wrote:
> > >> > * gnu/packages/gnupg.scm (libgcrypt): Update to 1.7.1
> > >>
> > >> This looks good to me. What branch should it go on?
> > >>
> > >
> > > either core-updates or core-updates-next
> >
> > The latter please. :-)
>
> Okay, in that case, can you rebase it on core-updates, ng0? Otherwise is
> won't apply cleanly due to trying to upgrade from 1.6.5 instad of 1.7.0.
>
This should be relatively easy when I have the gnupg branch still around,
otherwise I'll recreate it.
With the wording familiar to me yet sometimes not good to comprehend even
when I hear and parse it correctly when talking:
I should rebase the commit on the branch
`core-updates` which currently is at version 1.6.5?
--
♥Ⓐ ng0
For non-prism friendly talk find me on
psyced.org / loupsycedyglgamf.onion
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2016-06-17 18:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 19:53 [PATCH] gnu: libgcrypt update to 1.7.1 ng0
2016-06-16 15:40 ` Leo Famulari
2016-06-16 16:28 ` Efraim Flashner
2016-06-17 15:02 ` Ludovic Courtès
2016-06-17 17:43 ` Leo Famulari
2016-06-17 18:59 ` ng0 [this message]
2016-06-17 19:28 ` Leo Famulari
2016-06-17 22:44 ` ng0
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=20160617185923.GA24906@khazad-dum \
--to=ng0@we.make.ritual.n0.is \
--cc=guix-devel@gnu.org \
/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.