unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: zimoun <zimon.toutoune@gmail.com>, Marius Bakke <marius@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: branch master updated: gnu: nyxt: Update to 2-pre-release-3.
Date: Mon, 09 Nov 2020 10:29:57 +0100	[thread overview]
Message-ID: <87361i27ze.fsf@ambrevar.xyz> (raw)
In-Reply-To: <861rh3ypf0.fsf@gmail.com>

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

Understood, thanks!

I've just pushed a fix in 98a15c796afcc91894b7400b1d548cd50604db0c, so
Nyxt should be back to its pristine defintion.

Can't wait for staging to merge, the Common Lisp build-system is vastly
improved!

> > Is there an automated way to report the inputs changes from the
> > comment message?
>
> I'm not sure what you mean, can you elaborate?

Never mind, it's all clear now.

Thanks!

-- 
Pierre Neidhardt
https://ambrevar.xyz/

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

  reply	other threads:[~2020-11-09  9:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201020130843.10939.42161@vcs0.savannah.gnu.org>
2020-11-07 19:39 ` branch master updated: gnu: nyxt: Update to 2-pre-release-3 Marius Bakke
2020-11-07 19:46   ` Marius Bakke
2020-11-08  9:40     ` Pierre Neidhardt
2020-11-08 15:16       ` Marius Bakke
2020-11-09  7:12         ` zimoun
2020-11-09  9:29           ` Pierre Neidhardt [this message]
2020-11-09 21:14             ` Marius Bakke
2020-11-09 22:38               ` Marius Bakke
2020-11-10  9:01                 ` Pierre Neidhardt
2020-11-10  9:28                   ` Pierre Neidhardt
2020-11-10 19:22                   ` Marius Bakke
2020-11-10 19:59                     ` Pierre Neidhardt
2020-11-10 20:28                       ` Marius Bakke
2020-11-11  9:19                         ` Pierre Neidhardt
2020-11-11 12:43                           ` Pierre Neidhardt

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=87361i27ze.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=guix-devel@gnu.org \
    --cc=marius@gnu.org \
    --cc=zimon.toutoune@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 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).