unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Sahithi Yarlagadda <sahi@swecha.net>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel <guix-devel@gnu.org>, help-guix@gnu.org
Subject: Re: Next steps
Date: Mon, 25 Jun 2018 02:03:52 +0530	[thread overview]
Message-ID: <4b0e6b97-382a-9b2f-2b75-4b7a285b21d3@swecha.net> (raw)
In-Reply-To: <874lhs2avd.fsf@elephly.net>

Hi


On Monday 25 June 2018 01:52 AM, Ricardo Wurmus wrote:
> Hi Sahithi,
>
> I checked out the “wip-sahithi” branch and ran this command in a
> terminal (urxvt):
>
>     ./pre-inst-env guix build --check --no-grafts hello
>
> I do see colours for phase start and end notices, so the code is fine.
It worked for me now, when i tested it by checking out to wip-sahithi
branch.
> What terminal are you using?  Did this not work for you before?  What
> has changed since?
Gnome terminal
It worked for me earlier as well, i tested the code by building the
hello package before sending the patch.

Unsure why it dint work, i did couple of changes and reverted back
thought. Seems i missed something out.
>
> --
> Ricardo
>
>

-- 
Regards
Sahithi

      reply	other threads:[~2018-06-24 20:34 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <8ea5d026-fab9-7b12-198e-610ad7743cb2@swecha.net>
     [not found] ` <87fu1zznl3.fsf@elephly.net>
     [not found]   ` <f76f5ced-df02-fdcd-0a7a-37565d5d8605@swecha.net>
     [not found]     ` <87bmcnzjsp.fsf@elephly.net>
     [not found]       ` <18408eca-ad0b-111a-0ef6-ab452c9ca89c@swecha.net>
     [not found]         ` <878t7ryxvf.fsf@elephly.net>
     [not found]           ` <02e1a59a-ebc1-dfce-e1d6-22e97e742214@swecha.net>
     [not found]             ` <874lifypeb.fsf@elephly.net>
     [not found]               ` <648f81fc-0607-2c3b-f9a3-ca3b29cd637b@swecha.net>
     [not found]                 ` <87bmck22uz.fsf@elephly.net>
     [not found]                   ` <c2401637-c975-d416-e3a2-7b1535924c61@swecha.net>
     [not found]                     ` <8736xv1xvq.fsf@elephly.net>
     [not found]                       ` <64dfaf0c-3bcf-7b76-5831-b1c41d3f5563@swecha.net>
     [not found]                         ` <CAE4v=pjiR2fVN3SoA+NqSt4T9VEvM9Gfsz9OUPW=7X9RnNE7mg@mail.gmail.com>
     [not found]                           ` <c1a084e9-b888-1d01-b1fe-3e423169e750@swecha.net>
     [not found]                             ` <877en4ccut.fsf@elephly.net>
     [not found]                               ` <2b03fcec-c2d8-0604-156c-70fe7643a6cb@swecha.net>
     [not found]                                 ` <87zhzzbqn6.fsf@elephly.net>
     [not found]                                   ` <8f509759-c798-a150-bf5a-9b13cd07ac5b@swecha.net>
     [not found]                                     ` <87lgbibir5.fsf@elephly.net>
     [not found]                                       ` <564233bd-9511-7f84-3350-6a3a905534a8@swecha.net>
     [not found]                                         ` <87r2l767sg.fsf@elephly.net>
2018-06-24 18:25                                           ` Next steps Sahithi Yarlagadda
2018-06-24 20:22                                             ` Ricardo Wurmus
2018-06-24 20:33                                               ` Sahithi Yarlagadda [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=4b0e6b97-382a-9b2f-2b75-4b7a285b21d3@swecha.net \
    --to=sahi@swecha.net \
    --cc=guix-devel@gnu.org \
    --cc=help-guix@gnu.org \
    --cc=rekado@elephly.net \
    /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).