From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: "Wiktor Żelazny" <wz@freeshell.de>
Cc: 37603@debbugs.gnu.org
Subject: [bug#37603] [PATCH] gnu: Add aha.
Date: Thu, 03 Oct 2019 16:47:07 +0200 [thread overview]
Message-ID: <87wodl51jo.fsf@nckx> (raw)
In-Reply-To: <20191003141529.3940-1-wz@freeshell.de>
[-- Attachment #1: Type: text/plain, Size: 1496 bytes --]
Wiktor,
Thanks for the patch! This isn't a review, just an answer to your
question:
Wiktor Żelazny 写道:
> Hi, This is the first time that I’m submitting something that
> uses the
> git-fetch method. I tried to follow the manual. Unfortunately,
> it does
> not explain the role of this "0.9" string. I noticed that other
> contributors use various values. I left it at "0.9".
It's not a random value; it's the last ‘real’ release, think of it
as ‘release 0.9 + some more commits that were needed for some
reason’. If the project has never seen a release, ‘0.0.0’ is
used. You'll find that this is quite common, too.
At https://github.com/theZiz/aha/releases, we can see that the
last release before this commit was ‘0.5’, so that's what you
should use.
However: we prefer packaging releases, not arbitrary commits. Why
not package 0.5? If it's because it's old (it is) and missing
cool features, consider asking the author to cut a new release.
Whatever the case, please note the reason in a comment: ‘The last
release 0.5 is missing the vital foo feature and/or crashes on
Fridays’.
Since I'm here (still not a review! :-):
> + (revision "1")) ;Guix package revision
I know you probably copied this from elsewhere, but don't think
this comment adds anything.
> + (url "git://github.com/theZiz/aha.git")
Please use https:// instead of git://.
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-10-03 14:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-03 14:15 [bug#37603] [PATCH] gnu: Add aha Wiktor Żelazny
2019-10-03 14:47 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
2019-10-04 13:18 ` Wiktor Żelazny
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=87wodl51jo.fsf@nckx \
--to=guix-patches@gnu.org \
--cc=37603@debbugs.gnu.org \
--cc=wz@freeshell.de \
/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).