From: dpg <doubleplusgood23@gmail.com>
To: ludo@gnu.org
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Re: [PATCH] gnu: Add python2-gyp
Date: Mon, 05 Feb 2018 15:33:51 -0500 [thread overview]
Message-ID: <1517862831.6194.5.camel@gmail.com> (raw)
In-Reply-To: <87bmh3d17c.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1152 bytes --]
> Hi doubleplusgood23,
>
> doubleplusgood23@gmail.com skribis:
>
> > From 1eff5aea55f171a09ab65bd7f75e39cd05ffd88b Mon Sep 17 00:00:00 2001
> > From: dpg <doubleplusgood23@gmail.com>
> > Date: Fri, 2 Feb 2018 20:44:32 -0500
> > Subject: [PATCH 1/2] Initial changes (not tested)
>
> Not very confidence-inspiring. :-)
>
> Please take a look at:
>
> https://www.gnu.org/software/guix/manual/html_node/Submitting-Patches.html
>
> It’s a good idea to send patches that you think are ready. If you have
> issues while packaging, it’s better to ask for help on specific issues
> on help-guix@gnu.org and/or IRC.
>
> Thanks,
> Ludo’.
Hello! Thanks for looking at my patch.
The initial patch there was just uploading a skeleton over git so I could debug
on my guix laptop. I was trying to squash the commit properly but clearly I
messed up. I can assure you the commit has been through the linter, has had
repeated builds, and is functional as a library. This is just a single patch for
my larger goal to package Telegram, so it can sit on the backburner for a bit.
Thanks!
--
dpg
PGP Key: DA3ABDDC176CEF90
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 841 bytes --]
next prev parent reply other threads:[~2018-02-05 20:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-03 4:20 [PATCH] gnu: Add python2-gyp doubleplusgood23
2018-02-05 13:18 ` Ludovic Courtès
2018-02-05 20:33 ` dpg [this message]
2018-02-05 22:39 ` dpg
2018-02-05 23:11 ` Leo Famulari
2018-02-05 23:23 ` dpg
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=1517862831.6194.5.camel@gmail.com \
--to=doubleplusgood23@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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.