all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: 07/07: guix: python-build-system: Fix an outdated comment.
Date: Thu, 13 Oct 2016 15:39:05 -0400	[thread overview]
Message-ID: <20161013193905.GA8814@jasmine> (raw)
In-Reply-To: <87eg3kyrie.fsf@netris.org>

On Thu, Oct 13, 2016 at 03:32:09PM -0400, Mark H Weaver wrote:
> h.goebel@crazy-compilers.com (Hartmut Goebel) writes:
> 
> > htgoebel pushed a commit to branch master
> > in repository guix.
> >
> > commit 635a7af45d6e2105ad65d1a9531126cc232a2a50
> > Author: Hartmut Goebel <h.goebel@crazy-compilers.com>
> > Date:   Sun Oct 2 18:48:56 2016 +0200
> >
> >     guix: python-build-system: Fix an outdated comment.
> >     
> >     The python-build-system uses phases the build and install, but not
> >     configure. So the old comment was plain wrong since Sept. 2013, when the build
> >     phase has been added.
>
> This change triggered over 6300 rebuilds on 'master'.  I reverted it.
> Please beware that changing some files in guix/build/*.scm can trigger a
> large number of rebuilds, because some of these files are implicitly
> used as inputs to a large number of builds.

Sorry, I didn't realize that altering comments here would have an
effect; I would have warned Hartmut if I had.

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

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20161013152324.1276.70078@vcs.savannah.gnu.org>
     [not found] ` <20161013152324.EF9C7220170@vcs.savannah.gnu.org>
2016-10-13 19:32   ` 07/07: guix: python-build-system: Fix an outdated comment Mark H Weaver
2016-10-13 19:39     ` Leo Famulari [this message]
2016-10-13 20:45       ` Danny Milosavljevic
2016-10-15 22:16         ` Ludovic Courtès
2016-10-14  7:55       ` 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=20161013193905.GA8814@jasmine \
    --to=leo@famulari.name \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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.