all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: guix-devel <guix-devel@gnu.org>
Subject: Where to queue patches for staging? (was: Is staging open again?)
Date: Tue, 6 Mar 2018 21:45:15 +0100	[thread overview]
Message-ID: <aa4e98b0-c23f-5a24-617f-f72a8a97a8df@crazy-compilers.com> (raw)
In-Reply-To: <87a7vl16ht.fsf@fastmail.com>

Am 06.03.2018 um 18:03 schrieb Marius Bakke:
> Staging is nearly fully built, so it will have to wait until next round.
> Generally, branches 'close' once a Hydra evaluation starts.  Check in
> here for progress: <https://hydra.gnu.org/jobset/gnu/staging>.

This sound complicated for the occasional (staging-) contributor.

How should I determine when the next round is about to start? I can't
even spot that "staging is nearly fully built" and hydra's web-front-end
is slow. Further I do not have the time for monitoring hydra and catch
the time-window then I can push my commit. For me this does not work out
- and I assume for others if doesn't, too.

Is there some queue-for-staging branch where I can commit this patch to?
Or some other means, like setting some bug-status?

-- 
Regards
Hartmut Goebel

| Hartmut Goebel          | h.goebel@crazy-compilers.com               |
| www.crazy-compilers.com | compilers which you thought are impossible |

  reply	other threads:[~2018-03-06 20:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-05 11:43 Is staging open again? Hartmut Goebel
2018-03-06 17:03 ` Marius Bakke
2018-03-06 20:45   ` Hartmut Goebel [this message]
2018-03-07 14:20     ` Where to queue patches for staging? (was: Is staging open again?) Marius Bakke
2018-03-08 17:19       ` Where to queue patches for staging? Hartmut Goebel

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=aa4e98b0-c23f-5a24-617f-f72a8a97a8df@crazy-compilers.com \
    --to=h.goebel@crazy-compilers.com \
    --cc=guix-devel@gnu.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.