all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Sharlatan Hellseher <sharlatanus@gmail.com>
Cc: 64287-done@debbugs.gnu.org, Tobias Geerinckx-Rice <me@tobias.gr>
Subject: bug#64287: Scheduled monthly update for (gnu packages astronomy)
Date: Mon, 24 Jul 2023 20:30:36 +0200	[thread overview]
Message-ID: <ZL7DTJpcPB6fvlAf@jurong> (raw)
In-Reply-To: <CAO+9K5owNUargZX_NSi1YNJCwbmzNm_LFx=K65eGqvBjsN47TA@mail.gmail.com>

Hello Oleg,

Am Mon, Jul 24, 2023 at 06:36:18PM +0100 schrieb Sharlatan Hellseher:
> This issue may be closed  https://issues.guix.gnu.org/64287 as Tobias
> applied all of it's patches.

good, closing it with this email by cc-ing 64287-done@debbugs.gnu.org.

> I'm not sure about the reason of splittingt them into smaller ones, it
> may be a question to him :-)

Well, it makes sense to separate package updates from package rewrites,
like going from old style to gexps. For instance if the latter induce
a lot of whitespace changes and the former just a version and hash
update, they are easier to review separately. Then ultimately these are
also matters of personal taste...

> I'll rebase patches from https://issues.guix.gnu.org/64201 to the
> current master branch and sent V2, hope they are look ok.

Great, hopefully QA will catch up soon so we can simply apply patches
with a green button.

Andreas





  reply	other threads:[~2023-07-24 18:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-27 18:37 Scheduled monthly update for (gnu packages astronomy) Sharlatan Hellseher
2023-07-02 20:36 ` Ludovic Courtès
2023-07-24  8:53   ` Andreas Enge
2023-07-24 17:36     ` Sharlatan Hellseher
2023-07-24 18:30       ` Andreas Enge [this message]
2023-07-27 18:58       ` Sharlatan Hellseher

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=ZL7DTJpcPB6fvlAf@jurong \
    --to=andreas@enge.fr \
    --cc=64287-done@debbugs.gnu.org \
    --cc=me@tobias.gr \
    --cc=sharlatanus@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.