unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Brett Gilio <brettg@posteo.net>
To: Jesse Gibbons <jgibbons2357@gmail.com>
Cc: 38554@debbugs.gnu.org
Subject: [bug#38554] [PATCH 0/5]  Update python-hy to 0.17.0
Date: Mon, 09 Dec 2019 22:25:34 -0600	[thread overview]
Message-ID: <87k174n6wx.fsf@posteo.net> (raw)
In-Reply-To: <660a10a1f02b4818a28dfea58b544956437d4b66.camel@gmail.com> (Jesse Gibbons's message of "Mon, 09 Dec 2019 19:29:58 -0700")

Jesse Gibbons <jgibbons2357@gmail.com> writes:

> The next five patches:
> - add dependencies for python-hy 0.17.0 (patches 1,2)
> - update python-hy from 0.13.0 to 0.17.0 (patch 3)
> - add dependencies for python2-hy 0.17.0 (patches 4,5)
>
>
> This will be the last version of python-hy to support python 2. If it is
> better to drop python2-hy now, simply omit patches 4 and 5, and remove
> python2-hy.

Hy Jesse! (Haha.)

Thank you for your patch series. I am sorry for the delay and the lack
of communication regarding your bug report. I could imagine this is
really frustrating. There are some corrections that I think need to be
made before we go forward, and for the sake of education I would like to
propose some revisions. Once we get these revisions, I think we will be
golden for a push to master! So bare with me.

First off, _USUALLY_ we have the package-for-python2 derivatives in the
same commits as the package indicating the original. Thus, your
python2-* patches (4 & 5) can be squashed into their originating commits
(1 & 2) respectively.

In patch 1: You indicate your copyright email as such:

--8<---------------cut here---------------start------------->8---
;;; Copyright © 2019 Jesse Gibbons <jgibbons2357+guix@gmail.com>
--8<---------------cut here---------------end--------------->8---

Is this correct? Just seems odd to me.

Also in that patch you have too many white space return indications between the
preceeding package, and you have white space return at the EOF. This should be
reduced to one and none, respectively. Next, if you could run `guix
lint` on this package. Your synopsis and description sections are
identical and do not conform to our guidelines. I suspect this was just
the default from running `guix import pypi`.

If you need help with making synopsis and descriptions, here is the
relevant documentation:
https://guix.gnu.org/manual/en/html_node/Synopses-and-Descriptions.html

In patch 2: There should be a white space return before the package in
this case, but was likely cut off from the improper EOF return in patch
1. Otherwise, this package looks okay aside from the issue with the
synopsis and description.

Lastly, all of the commit messages need a period at the end. And the
sub-header message for the patch which bumps Hy to 0.17 needs a period
as well. You could also remove the redundant [inputs] section and simply
make a comma-separated-list of new inputs. Also, if you could add
something like,

--8<---------------cut here---------------start------------->8---
Fixes: <link-to-original-bug-report>.
--8<---------------cut here---------------end--------------->8---

to the patch that updates Hy, that way we can know where this patch
series is predicated from. That would be superb!

Once we get these easy changes done we will push! If you could send your
revisions with something like:

--8<---------------cut here---------------start------------->8---
[PATCH v2 x/3]
--8<---------------cut here---------------end--------------->8---


Again, I apologize for the radio silence.

-- 
Brett M. Gilio
Homepage -- https://scm.pw/
GNU Guix -- https://guix.gnu.org/

  parent reply	other threads:[~2019-12-10  4:26 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-10  2:29 [bug#38554] [PATCH 0/5] Update python-hy to 0.17.0 Jesse Gibbons
2019-12-10  2:35 ` [bug#38554] [PATCH 1/5] Add python-fastentrypoints Jesse Gibbons
2019-12-10  2:36 ` [bug#38554] [PATCH 2/5] Add python-funcparserlib Jesse Gibbons
2019-12-10  2:37 ` [bug#38554] [PATCH 3/5] Update python-hy to 0.17.0 Jesse Gibbons
2019-12-10  2:37 ` [bug#38554] [PATCH 4/5] Add python2-fastentrypoints Jesse Gibbons
2019-12-12 17:18   ` zimoun
2019-12-16  0:37     ` Jesse Gibbons
2019-12-10  2:38 ` [bug#38554] [PATCH 5/5] Add python2-funcparserlib Jesse Gibbons
2019-12-10  4:25 ` Brett Gilio [this message]
2019-12-10 21:59   ` [bug#38554] [PATCH 0/5] Update python-hy to 0.17.0 Jesse Gibbons
2019-12-12 17:23     ` zimoun
2019-12-21 17:14 ` [bug#38554] [PATCH v2 1/3] gnu: Add python-fastentrypoints Jesse Gibbons
2019-12-21 17:14 ` [bug#38554] [PATCH v2 2/3] gnu: Add python-funcparserlib Jesse Gibbons
2019-12-21 17:14 ` [bug#38554] [PATCH v2 3/3] gnu: python-hy: Update to 0.17.0 Jesse Gibbons
2019-12-25  7:27   ` bug#38554: " Brett Gilio

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=87k174n6wx.fsf@posteo.net \
    --to=brettg@posteo.net \
    --cc=38554@debbugs.gnu.org \
    --cc=jgibbons2357@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).