unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org
Subject: Re: 01/03: gnu: wxwidgets: Add libxtst to inputs.
Date: Sat, 10 Jun 2023 23:17:44 -0400	[thread overview]
Message-ID: <87wn0aadrb.fsf@gmail.com> (raw)
In-Reply-To: <87sfb31qqp.fsf@cbaines.net> (Christopher Baines's message of "Wed, 07 Jun 2023 11:59:31 +0100")

Hi Christopher,

Christopher Baines <mail@cbaines.net> writes:

> guix-commits@gnu.org writes:
>
>> apteryx pushed a commit to branch master
>> in repository guix.
>>
>> commit ec9f15b158300da3a77ce02cd2267222f435e80f
>> Author: Maxim Cournoyer <maxim.cournoyer@gmail.com>
>> AuthorDate: Tue Jun 6 12:12:40 2023 -0400
>>
>>     gnu: wxwidgets: Add libxtst to inputs.
>>
>>     WxWidgets was already built with XTest support, but mostly by luck, via
>>     propagation of libxtst from GTK's propagated at-spi2-core package.  Make it an
>>     explicit input.
>>
>>     * gnu/packages/wxwidgets.scm (wxwidgets) [inputs]: Add libxtst.
>> ---
>>  gnu/packages/wxwidgets.scm | 1 +
>>  1 file changed, 1 insertion(+)
>
> Did this need to go straight to the master branch?
>
> → guix refresh -l wxwidgets
> Building the following 217 packages would ensure 456 dependent packages are rebuilt: ...
>
> That to me says this should go to staging.

Correct.  Except there's no staging branch anymore.  I guess we should
create one?  :-)

-- 
Thanks,
Maxim


  reply	other threads:[~2023-06-11  3:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <168610879676.2825.9044237296073582277@vcs2.savannah.gnu.org>
     [not found] ` <20230607033317.826FCC23EDC@vcs2.savannah.gnu.org>
2023-06-07 10:59   ` 01/03: gnu: wxwidgets: Add libxtst to inputs Christopher Baines
2023-06-11  3:17     ` Maxim Cournoyer [this message]
2023-06-11  8:44       ` Rebasing or merging? [was: Re: 01/03: gnu: wxwidgets: Add libxtst to inputs.] Andreas Enge
2023-06-11 21:25         ` Maxim Cournoyer
2023-06-11 22:40           ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-06-12  0:47             ` Maxim Cournoyer
2023-06-12  1:10               ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-06-12 12:22                 ` Maxim Cournoyer
2023-06-12 13:13                 ` Andreas Enge
2023-06-12 13:47                   ` Maxim Cournoyer
2023-06-13  2:07               ` Leo Famulari
2023-06-14  1:32                 ` Maxim Cournoyer
2023-06-20 17:15                   ` Giovanni Biscuolo
2023-06-20 20:39                     ` Maxim Cournoyer
2023-06-21  7:36                       ` Josselin Poiret
2023-06-26 13:26                         ` Maxim Cournoyer
2023-06-20 16:32                 ` Giovanni Biscuolo
2023-06-11  9:25       ` 01/03: gnu: wxwidgets: Add libxtst to inputs Christopher Baines
2023-06-11 21:20         ` Maxim Cournoyer

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=87wn0aadrb.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mail@cbaines.net \
    /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).