unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Marius Bakke <mbakke@fastmail.com>
To: Leo Famulari <leo@famulari.name>, guix-devel@gnu.org
Subject: Re: 04/05: gnu: xorg-server: Update to 1.19.3.
Date: Thu, 06 Apr 2017 18:11:02 +0200	[thread overview]
Message-ID: <874ly1a549.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20170406152432.GA6569@jasmine>

[-- Attachment #1: Type: text/plain, Size: 917 bytes --]

Leo Famulari <leo@famulari.name> writes:

> On Thu, Apr 06, 2017 at 10:04:12AM -0400, Marius Bakke wrote:
>> mbakke pushed a commit to branch staging
>> in repository guix.
>> 
>> commit 7c42cc7738cb28f393b17f9074a264607456c012
>> Author: Marius Bakke <mbakke@fastmail.com>
>> Date:   Thu Apr 6 15:42:15 2017 +0200
>> 
>>     gnu: xorg-server: Update to 1.19.3.
>>     
>>     * gnu/packages/xorg.scm (xorg-server, xorg-server-xwayland): Update to 1.19.3.
>>     [native-inputs]: Remove FONT-UTIL, LIBTOOL, AUTOMAKE and AUTOCONF.
>>     [arguments]: Remove 'bootstrap' phase.
>
> This can go straight to master, right?

I don't think so, because of the inputs and arguments change, which
would affect xorg-server-1.19.2 as well (and cause the build to fail).

Commit 3433413b18f02436eb8459d097947257ac6973f7 addresses this, so
future xorg-server updates should indeed be eligible for 'master'.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  reply	other threads:[~2017-04-06 16:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20170406140411.14339.19187@vcs0.savannah.gnu.org>
     [not found] ` <20170406140413.158452084C@vcs0.savannah.gnu.org>
2017-04-06 15:24   ` 04/05: gnu: xorg-server: Update to 1.19.3 Leo Famulari
2017-04-06 16:11     ` Marius Bakke [this message]
2017-04-06 21:05       ` 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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874ly1a549.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
    --to=mbakke@fastmail.com \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).