From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Releasing 0.9.1
Date: Sun, 07 Feb 2016 21:44:19 +0100 [thread overview]
Message-ID: <87lh6ws124.fsf@gnu.org> (raw)
In-Reply-To: <877figwusz.fsf@elephly.net> (Ricardo Wurmus's message of "Sun, 07 Feb 2016 13:48:12 +0100")
Ricardo Wurmus <rekado@elephly.net> skribis:
> Ben Woodcroft <b.woodcroft@uq.edu.au> writes:
[...]
>> >[Ricardo] proposed recently to pass a package object instead of a
>> package name to ‘latest-release’. We should do that ideally before this
>> patch goes in, or otherwise soon.
>>
>> Is there any update for this Ricardo? Do we just go ahead and use the
>> old style for the time being?
>
> Oh, I dropped the ball there. It’s very simple to do this, but I don’t
> think I can do it today, I’m afraid. I can try to do it tomorrow, but I
> don’t think it should block the GitHub updater.
>
> I could easily patch the GitHub updater along with all the other
> updaters that would need to be adapted, so my vote is for using the old
> style for now and switching to package objects soon thereafter.
Fine with me!
Ben: can you post the latest version of the patch? Or was it already
OK?
Ludo’.
next prev parent reply other threads:[~2016-02-07 20:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 13:46 Releasing 0.9.1 Ludovic Courtès
2016-02-05 13:51 ` Andreas Enge
2016-02-07 12:13 ` Ben Woodcroft
2016-02-07 12:48 ` Ricardo Wurmus
2016-02-07 20:44 ` Ludovic Courtès [this message]
2016-02-07 20:54 ` Ben Woodcroft
2016-02-08 21:21 ` Mathieu Lirzin
2016-02-25 17:51 ` Ludovic Courtès
2016-02-25 18:04 ` Ricardo Wurmus
2016-02-25 19:27 ` Leo Famulari
2016-02-26 23:15 ` Ludovic Courtès
2016-02-25 20:11 ` Andreas Enge
2016-02-26 23:16 ` Ludovic Courtès
2016-03-09 13:14 ` Ludovic Courtès
2016-03-09 14:41 ` Ludovic Courtès
2016-03-10 16:23 ` Ludovic Courtès
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=87lh6ws124.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@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.
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.