From: Leo Famulari <leo@famulari.name>
To: guix-devel@gnu.org
Cc: kuba@kadziolka.net, mail@nicolasgoaziou.fr
Subject: Re: branch staging updated (5aeee07 -> 104151f)
Date: Sat, 30 Jan 2021 18:20:35 -0500 [thread overview]
Message-ID: <YBXpw8a7UwJDv/Uq@jasmine.lan> (raw)
In-Reply-To: <20210129220535.30446.38250@vcs0.savannah.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 882 bytes --]
On Fri, Jan 29, 2021 at 05:05:35PM -0500, guix-commits@gnu.org wrote:
> htgoebel pushed a change to branch staging
> in repository guix.
>
> from 5aeee07 gnu: VLC: Remove obsolete patch.
> new 9085260 guix: qt-build-system, qt-utils: Unify wrapping of qt-programs.
> new 4ecc2a2 guix: qt-utils: Wrapped executables honor user's envvars.
> new 094b6ac build-system: qt: Exclude useless inputs from wrapped variables.
> new 104151f guix: qt-utils: Don't include useless inputs in wrapped variables.
The staging branch is frozen [0] so I reverted these commits and pushed
them to staging-next.
I wonder what we can do to communicate the branch status. Right now it's
not easy to figure out, aside from asking around. Nicolas Goaziou
suggested using a Git hook.
[0]
https://lists.gnu.org/archive/html/guix-devel/2020-12/msg00157.html
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next parent reply other threads:[~2021-01-30 23:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210129220535.30446.38250@vcs0.savannah.gnu.org>
2021-01-30 23:20 ` Leo Famulari [this message]
2021-01-30 23:37 ` branch staging updated (5aeee07 -> 104151f) Mark H Weaver
2021-01-31 5:18 ` Leo Famulari
2021-01-31 9:59 ` Jakub Kądziołka
2021-01-31 21:09 ` Mark H Weaver
2021-02-01 11:14 ` Hartmut Goebel
2021-02-01 11:28 ` Efraim Flashner
2021-02-01 19:39 ` Mark H Weaver
2021-02-01 20:43 ` Christopher Baines
2021-02-01 20:56 ` 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=YBXpw8a7UwJDv/Uq@jasmine.lan \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=kuba@kadziolka.net \
--cc=mail@nicolasgoaziou.fr \
/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).