all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: 宋文武 <iyzsong@member.fsf.org>
Cc: guix-devel@gnu.org
Subject: Re: Gnome-updates
Date: Mon, 2 May 2016 14:35:51 -0400	[thread overview]
Message-ID: <20160502183551.GC10321@jasmine> (raw)
In-Reply-To: <87wpncldor.fsf@member.fsf.org>

On Mon, May 02, 2016 at 10:47:16PM +0800, 宋文武 wrote:
> Thanks for the review.
> I have rebase it upon master again with the one log change but
> leave out the poppler CVE-2015-8868 fix (it's in 0.42.0) in master.
> (I can't use force push so I delete and push it again..)

I'm just joining this conversation. Do you want me to commit a different
poppler bug-fix to gnome-updates? That could be the branch where we
"undo" this graft.

  reply	other threads:[~2016-05-02 18:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-26 17:37 Gnome-updates Andreas Enge
2016-04-27 13:11 ` Gnome-updates Ludovic Courtès
2016-04-27 14:31   ` Gnome-updates 宋文武
2016-04-27 14:58     ` Gnome-updates Ludovic Courtès
2016-04-27 19:33     ` Gnome-updates Ludovic Courtès
2016-04-30  8:33       ` Gnome-updates 宋文武
2016-05-02  8:17         ` Gnome-updates Ludovic Courtès
2016-05-02 14:47           ` Gnome-updates 宋文武
2016-05-02 18:35             ` Leo Famulari [this message]
2016-05-03  0:38               ` Gnome-updates 宋文武
2016-05-03 17:32                 ` Gnome-updates Efraim Flashner
2016-05-03 21:07                   ` Gnome-updates Leo Famulari
2016-05-03 11:35             ` Gnome-updates Ludovic Courtès
2016-05-11  8:08               ` Gnome-updates Andreas Enge
     [not found] <20170513232810.28268.54349@vcs0.savannah.gnu.org>
2017-05-14 12:45 ` gnome-updates Ludovic Courtès
2017-05-14 15:35   ` gnome-updates Marius Bakke
2017-05-14 17:04     ` gnome-updates Leo Famulari
2017-05-24 20:17       ` gnome-updates Marius Bakke
2017-05-24 21:07         ` gnome-updates Leo Famulari

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=20160502183551.GC10321@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=iyzsong@member.fsf.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.