From: Leo Famulari <leo@famulari.name>
To: Eric Bavier <ericbavier@openmailbox.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] Clean all .go in clean-go
Date: Fri, 16 Sep 2016 02:00:17 -0400 [thread overview]
Message-ID: <20160916060017.GD14289@jasmine> (raw)
In-Reply-To: <20160916001540.617d9a54@openmailbox.org>
On Fri, Sep 16, 2016 at 12:15:40AM -0500, Eric Bavier wrote:
> Another issue that I thought of that's posed by these stray .go files,
> which isn't only a problem when acting as a wizard: introducing a new
> module import when adding a package, only to have that module
> moved/renamed before pushing your change. I suppose it is a corner
> case, but it did happen to me recently, in 2e3f18511, which 宋文武
> kindly fixed in 19b2ea1b6. The problem was that between the time I
> originally packaged tomb and the time I pushed the commit,
> gnu/packages/zsh.scm was consolidated into gnu/packages/shells.scm. I
> had done a `make clean-go && make` before pushing, as I always do, but
> since clean-go didn't remove gnu/packages/zsh.go the subsequent `make`
> didn't complain of a missing module.
I accidentally did this to myself in c41d97bed6 (gnu: mupdf: Update to
1.9a.).
next prev parent reply other threads:[~2016-09-16 6:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 23:20 [PATCH] Clean all .go in clean-go Eric Bavier
2016-08-31 23:20 ` [PATCH] build: Clean all .go files " Eric Bavier
2016-09-01 1:10 ` [PATCH] Clean all .go " Mathieu Lirzin
2016-09-01 10:03 ` David Craven
2016-09-01 12:37 ` Ludovic Courtès
2016-09-02 1:30 ` Eric Bavier
2016-09-02 12:42 ` Ludovic Courtès
2016-09-16 5:15 ` Eric Bavier
2016-09-16 6:00 ` Leo Famulari [this message]
2016-09-20 5:20 ` Ludovic Courtès
2017-11-07 1:06 ` myglc2
2017-11-08 10:49 ` Vincent Legoll
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=20160916060017.GD14289@jasmine \
--to=leo@famulari.name \
--cc=ericbavier@openmailbox.org \
--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 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).