all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Omar Radwan <toxemicsquire4@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add urwid
Date: Tue, 03 Feb 2015 22:07:04 +0100	[thread overview]
Message-ID: <87wq3yn1qf.fsf@gnu.org> (raw)
In-Reply-To: <CAMwaQAKUzHoeoa-gw-DmtatZ9zMSHqtaysdnAJ7A51qdbW5n5g@mail.gmail.com> (Omar Radwan's message of "Tue, 3 Feb 2015 09:20:01 -0800")

Omar Radwan <toxemicsquire4@gmail.com> skribis:

>>I'm sorry, but we are failing to >communicate, and I don't have any >more
>>time to spend on this.  I have pushed >commit e99f421185 based on your
>>preliminary work.  It adds two >packages: python-urwid for Python 3, >and
>>python2-urwid for Python 2.
>
> Sorry for the miscommunication. I'll do better next time. Thanks for the
> commit push. I can start working on wicd

Cool.  Thanks for urwid, and thanks to Mark for helping out!

One way to avoid miscommunication in the future would be to read the
“Submitting Patches” section in ‘HACKING’ and to look at existing
commits for the conventions to follow.  Another thing would be to avoid
HTML emails and top-posting, which are inconvenient for the reader.

Ludo’.

      reply	other threads:[~2015-02-03 21:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-01 22:56 [PATCH] gnu: Add urwid Omar Radwan
2015-02-01 23:23 ` Omar Radwan
2015-02-02  0:14   ` Omar Radwan
2015-02-02  2:32     ` Mark H Weaver
2015-02-02  4:57       ` Omar Radwan
2015-02-02  5:42         ` Mark H Weaver
2015-02-02 17:46           ` Omar Radwan
2015-02-02 17:59             ` Andreas Enge
2015-02-03  3:37               ` Omar Radwan
2015-02-03  4:42                 ` Mark H Weaver
2015-02-03  4:48                   ` Omar Radwan
2015-02-03  5:37                     ` Mark H Weaver
2015-02-03 17:20                       ` Omar Radwan
2015-02-03 21:07                         ` Ludovic Courtès [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87wq3yn1qf.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=toxemicsquire4@gmail.com \
    /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.