all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: help-guix@gnu.org
Subject: Re: Hwo to debug and teacking builds?
Date: Wed, 12 Apr 2017 18:32:34 -0700	[thread overview]
Message-ID: <87d1chozwt.fsf@gmail.com> (raw)
In-Reply-To: <58ED0610.3060008@crazy-compilers.com> (Hartmut Goebel's message of "Tue, 11 Apr 2017 18:36:32 +0200")

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

Hartmut Goebel <h.goebel@crazy-compilers.com> writes:

> Am 11.04.2017 um 17:40 schrieb Chris Marusich:
>> myglc2 <myglc2@gmail.com> writes:
>>
>>> On 03/28/2017 at 23:10 Chris Marusich writes:
>>>
>>> [...]
>>>
>>>>   export INFOPATH="$HOME/guix/doc${INFOPATH:+:}$INFOPATH"
>>> export INFOPATH="$HOME/guix/doc${INFOPATH:+:$INFOPATH}"
>> Yes, you're correct.  I mis-typed that.
>
> But isn't the result the same?

Maybe?  I typed this manually, and I meant to type what George
mentioned.  If what I typed was correct, then it was correct on
accident.

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  parent reply	other threads:[~2017-04-13  1:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-28  9:16 Hwo to debug and teacking builds? Hartmut Goebel
2017-03-28  9:52 ` Ludovic Courtès
2017-03-28 13:45   ` Catonano
2017-03-28 16:07     ` ng0
2017-03-28 18:11       ` Catonano
2017-03-28 18:24         ` ng0
2017-04-10  6:39         ` Ricardo Wurmus
2017-04-10  7:19           ` Catonano
2017-03-29  6:10     ` Chris Marusich
2017-03-29 10:36       ` Catonano
2017-04-11 14:15       ` myglc2
2017-04-11 15:40         ` Chris Marusich
2017-04-11 16:36           ` Hartmut Goebel
2017-04-11 19:01             ` myglc2
2017-04-13  1:32             ` Chris Marusich [this message]
2017-03-28 15:58   ` 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=87d1chozwt.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.
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.