unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: John Darrington <john@darrington.wattle.id.au>
To: Kei Kebreau <kei@openmailbox.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/1] Dbus update 1.10.12 for core-updates
Date: Mon, 10 Oct 2016 20:39:17 +0200	[thread overview]
Message-ID: <20161010183917.GA16280@jocasta.intra> (raw)
In-Reply-To: <871szohy7j.fsf@openmailbox.org>

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

On Mon, Oct 10, 2016 at 02:10:24PM -0400, Kei Kebreau wrote:
     
     Excuse my ignorance, but when is a patch considered significant enough
     to be updated on core-updates instead of master? Put another way, what
     is the purpose of core-updates?

Core updates is for those things near the root of the dependency tree.
Changing these things causes a large amount of other things to be rebuilt.
Therefore, the core-updates branch is built very much less frequently than
master.

J'



-- 
Avoid eavesdropping.  Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3 
fingerprint = 8797 A26D 0854 2EAB 0285  A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2016-10-10 18:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-10 17:44 [PATCH 0/1] Dbus update 1.10.12 for core-updates Leo Famulari
2016-10-10 17:44 ` [PATCH 1/1] gnu: dbus: Update to 1.10.12 Leo Famulari
2016-10-10 18:10 ` [PATCH 0/1] Dbus update 1.10.12 for core-updates Kei Kebreau
2016-10-10 18:39   ` John Darrington [this message]
2016-10-10 19:30     ` Kei Kebreau
2016-10-10 20:57 ` Ludovic Courtès
2016-10-12 16:41   ` Leo Famulari
2016-10-13 20:19     ` Ludovic Courtès
2016-10-14  3:01       ` 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=20161010183917.GA16280@jocasta.intra \
    --to=john@darrington.wattle.id.au \
    --cc=guix-devel@gnu.org \
    --cc=kei@openmailbox.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 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).