From: Chris Marusich <cmmarusich@gmail.com>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Real-world example for channels?
Date: Sun, 27 Jan 2019 16:49:01 -0800 [thread overview]
Message-ID: <87munla9oi.fsf@gmail.com> (raw)
In-Reply-To: <29d3b7b9-6d96-e132-e59e-ec7a5ccdd2f1@crazy-compilers.com> (Hartmut Goebel's message of "Sat, 26 Jan 2019 23:16:31 +0100")
[-- Attachment #1: Type: text/plain, Size: 463 bytes --]
Hartmut Goebel <h.goebel@crazy-compilers.com> writes:
> o What happens if files conflict? Which repo will take precedence?
I think the short answer is: for now, don't do that.
There was some discussion here about conflicts:
https://lists.gnu.org/archive/html/guix-devel/2018-10/msg00384.html
We basically agreed that for now, we should error out if there is a
conflict, but I don't know if that code has been implemented yet.
--
Chris
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2019-01-28 0:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-26 22:16 Real-world example for channels? Hartmut Goebel
2019-01-26 23:00 ` Ricardo Wurmus
2019-01-28 0:46 ` Chris Marusich
2019-01-28 6:57 ` Konrad Hinsen
2019-02-12 16:24 ` Ludovic Courtès
2019-02-13 5:41 ` Chris Marusich
2019-01-27 9:52 ` Efraim Flashner
2019-01-28 0:49 ` Chris Marusich [this message]
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=87munla9oi.fsf@gmail.com \
--to=cmmarusich@gmail.com \
--cc=h.goebel@crazy-compilers.com \
--cc=help-guix@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.
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).